@vercel/python-analysis
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Vercel migrated publishing from vercel-release-bot to GitHub Actions CI; SLSA attestation confirms legitimate CI/CD origin. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer (matt.straka) consistent with Vercel org transition; package has SLSA provenance backing the release. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Vercel monorepo packages consistently lack descriptions/keywords and share templated name shapes; this is a stable false positive for @vercel/* packages published by vercel-release-bot. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Official Vercel monorepo package; missing description is a cosmetic issue, not a malware signal. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:pip-requirements-js | AI (dependencies): pip-requirements-js is contextually appropriate for a Python analysis package that needs to parse pip requirements files. Legitimate use case. | ai | |
| phantom-deps | phantom-dep:@bytecodealliance/preview2-shim | AI (phantom-deps): @bytecodealliance/preview2-shim is a WASM component model shim used via the imports map and build pipeline, not a direct JS import. This pattern is stable for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.11.1 | 7 / 6 | |
| 0.11.0 | 7 / 6 | |
| 0.10.1 | 7 / 6 | |
| 0.10.0 | 7 / 6 | |
| 0.8.0 | 8 / 6 | |
| 0.4.1 | 8 / 6 | |
| 0.3.2 | 8 / 6 | |
| 0.3.1 | 8 / 6 | |
| 0.2.0 | 7 / 5 | |
| 0.1.1 | 7 / 6 |
v0.11.1
2 findingsThis version was published by a different npm account than previous versions on 2026-04-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
2 findingsMaintainer email '[email protected]' uses domain 'magic.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.