io.github.AliAkhtari78/spotifyscraper
version 3.9.2
- scanned 2026-10-16
- source github.com/AliAkhtari78/SpotifyScraper
- transport stdio
- files read 63
- methodology 0.2.0
- ruleset 0.1.1
100
100measured on 80% of this axis
22
56measured on 90% of this axis
83measured on 80% of this axis
The evidence
Every deduction below names the artefact that produced it. Nothing on this page was executed: the source was read, never run, and no running server was contacted.
Auth Posture
- authentication_model
stdio transport: the client launches the server as a subprocess, so the OS process boundary is the auth boundary — `03` §4 does not penalise absent auth here
- transport_security
declared transport: stdio — launched as a subprocess by the client, so the security boundary is the client process, not a network port (`03` §4)
- secret_handling
detect-secrets matched 124 credential-shaped string(s), every one from a keyword or entropy heuristic (Basic Auth Credentials, Hex High Entropy String, Secret Keyword). Those flag placeholders, variable names and content hashes as readily as credentials, so they do not establish the committed credential `03` §4's 0 asserts, and this sub-check is not scored; Basic Auth Credentials at docs/guides/async.md:129; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:42; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:47; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:52; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:57; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:67; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:72; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:77; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:82; Hex High Entropy String at src/spotify_scraper/api/pathfinder.py:87; …and 114 more matches
- authorization_granularity
28 tool registrations with conditional access logic present in the same source
Dependency Health
- uv.lockanyio 4.14.0 — PYSEC-2026-4025
transitive, CVSS 9.3, fixed in 4.14.2
https://osv.dev/vulnerability/PYSEC-2026-4025 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4145
transitive, CVSS 9.1, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4145 - uv.lockmcp 1.28.0 — PYSEC-2026-3483
direct, CVSS 7.6, fixed in 1.28.1
https://osv.dev/vulnerability/PYSEC-2026-3483 - uv.lockmcp 1.28.0 — GHSA-84m7-p3x7-pcfv
direct, CVSS 7.5, fixed in 1.30.0
https://osv.dev/vulnerability/GHSA-84m7-p3x7-pcfv - uv.lockurllib3 2.7.0 — PYSEC-2026-4177
transitive, CVSS 8.9, fixed in 2.8.0
https://osv.dev/vulnerability/PYSEC-2026-4177 - uv.lockcryptography 49.0.0 — PYSEC-2026-3552
transitive, CVSS 8.2, fixed in 50.0.0
https://osv.dev/vulnerability/PYSEC-2026-3552 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4183
transitive, CVSS 8.2, fixed in 2.15.0
https://osv.dev/vulnerability/PYSEC-2026-4183 - uv.lockvirtualenv 21.5.1 — PYSEC-2026-4013
transitive, CVSS 7.8, fixed in 21.7.13
https://osv.dev/vulnerability/PYSEC-2026-4013 - uv.lockvirtualenv 21.5.1 — PYSEC-2026-4011
transitive, CVSS 7.7, fixed in 21.7.12
https://osv.dev/vulnerability/PYSEC-2026-4011 - uv.lockurllib3 2.7.0 — PYSEC-2026-4175
transitive, CVSS 7.6, fixed in 2.8.0
https://osv.dev/vulnerability/PYSEC-2026-4175 - uv.lockpymdown-extensions 10.21.3 — PYSEC-2026-3654
transitive, CVSS 7.5, fixed in 11.0.1
https://osv.dev/vulnerability/PYSEC-2026-3654 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4143
transitive, CVSS 7.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4143 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4144
transitive, CVSS 7.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4144 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4149
transitive, CVSS 7.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4149 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4150
transitive, CVSS 7.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4150 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4151
transitive, CVSS 7.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4151 - uv.lockvirtualenv 21.5.1 — PYSEC-2026-4014
transitive, CVSS 7.3, fixed in 21.7.12
https://osv.dev/vulnerability/PYSEC-2026-4014 - uv.lockanyio 4.14.0 — PYSEC-2026-4023
transitive, CVSS 7.0, fixed in 4.14.2
https://osv.dev/vulnerability/PYSEC-2026-4023 - uv.lockurllib3 2.7.0 — PYSEC-2026-4176
transitive, CVSS 6.9, fixed in 2.8.0
https://osv.dev/vulnerability/PYSEC-2026-4176 - uv.lockanyio 4.14.0 — PYSEC-2026-4024
transitive, CVSS 6.8, fixed in 4.14.2
https://osv.dev/vulnerability/PYSEC-2026-4024 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4146
transitive, CVSS 6.5
https://osv.dev/vulnerability/PYSEC-2026-4146 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4152
transitive, CVSS 5.9, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4152 - uv.lockvirtualenv 21.5.1 — PYSEC-2026-4012
transitive, CVSS 5.8, fixed in 21.7.11
https://osv.dev/vulnerability/PYSEC-2026-4012 - uv.lockmkdocs-material 9.7.6 — PYSEC-2026-3864
transitive, CVSS 5.4, fixed in 9.7.7
https://osv.dev/vulnerability/PYSEC-2026-3864 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4140
transitive, CVSS 5.3, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4140 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4141
transitive, CVSS 5.3, fixed in 2.15.0
https://osv.dev/vulnerability/PYSEC-2026-4141 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4142
transitive, CVSS 5.3, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4142 - uv.lockpymdown-extensions 10.21.3 — PYSEC-2026-3609
transitive, CVSS 5.3, fixed in 11.0.0
https://osv.dev/vulnerability/PYSEC-2026-3609 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4147
transitive, CVSS 4.8, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4147 - uv.lockpyjwt 2.13.0 — PYSEC-2026-4148
transitive, CVSS 4.4, fixed in 2.14.0
https://osv.dev/vulnerability/PYSEC-2026-4148
Maintenance
- recency
last commit 112 day(s) before 2026-10-16
- issue_responsiveness
median over 3 issue(s) in the last 6 months: 43.3 day(s) to first maintainer comment
- release_cadence
median release gap 0 days (by releases), last release 112 day(s) ago
- bus_factor
sole maintainer, and no commit in over 90 days
- repository_signals
`03` §5 scores this by quartile WITHIN the server's category, which needs a distribution across every scanned server and so cannot be computed while scanning one. It is a post-pass over the crawl and that pass does not exist yet.
Transparency
- license
LICENSE present with no SPDX-License-Identifier tag; identified as 'MIT' from its text
- readme_quality
README.md: installation instructions (+25), exposed tools or resources enumerated (+30), states what the server does in the first 200 words (+20)
- declared_scopes
specific scope or access documentation is present, but `03` §7's 100 and 60 bands both compare it against scopes INFERRED from static analysis, which is not built yet. Scoring 100 on an empty inference would be a vacuous truth — 'all ∅ inferred scopes are documented'.
- changelog
CHANGELOG.md present
- security_contact
SECURITY.md present
Contest a finding
Every number here comes from a rule reading published source, and rules get things wrong. If something on this page is incorrect — or correct but mitigated by a check the rule cannot see — open an issue and we answer it in writing. A finding we got wrong is removed and the rule is fixed; one that stands is answered on the record.
Anyone can file: the maintainer, a researcher who disagrees with the classification, or a user who tested the server and could not reproduce it. Name this server and the rule or advisory ID shown beside the finding above. We aim to reply within five business days and to resolve within ten.