m3u8-parser
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Standard videojs org maintainer team rotation, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Artifact of stale diff baseline (v2.1.0), not real dormancy given 35 versions/1.1M downloads. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher stable 1110d+, consistent with legitimate org maintainer, not takeover. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in dev scripts/server.js loading package.json; not in runtime code and not a risk. | ai | |
| phantom-deps | phantom-dep:global | AI (phantom-deps): global is a declared runtime dep used indirectly via bundled output; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 7.2.0 | 3 / 10 | |
| 7.1.0 | 3 / 10 | |
| 7.0.0 | 3 / 10 | |
| 2.1.0 | 0 / 32 |
v7.1.0
2 findingsThis version was published by a different npm account (hswaminathan) than the most recent previously approved version (mjneil) on 2023-08-07. It has since remained available on npm for 1082 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsThis version was published by a different npm account (hswaminathan) than the most recent previously approved version (mjneil) on 2023-07-10. It has since remained available on npm for 1110 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.