mpd-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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:test/inheritAttributes.test.js | AI (source-diff): Base64 DRM PSSH test fixtures in unit tests, not hidden payloads. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change is old and stable, inconsistent with takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are from known Brightcove/MUX orgs consistent with this videojs package's ownership. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer rotation in a long-lived org package; publisher is a known prior maintainer. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived popular package; dormancy followed by org-level maintainer rotation is expected, not suspicious. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel runtime is loaded by convention via transpiled output; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 4 / 11 | |
| 1.3.1 | 4 / 11 | |
| 1.3.0 | 4 / 11 | |
| 1.2.2 | 4 / 11 | |
| 1.2.1 | 4 / 11 | |
| 1.2.0 | 4 / 11 | |
| 1.1.1 | 4 / 11 | |
| 1.1.0 | 4 / 11 | |
| 1.0.1 | 4 / 11 | |
| 1.0.0 | 4 / 11 |
v1.3.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (awaldron) than the most recent previously approved version (misterben) on 2023-12-08. It has since remained available on npm for 959 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.
v1.2.2
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (walterseymourbc) than the most recent previously approved version (misterben) on 2023-08-30. It has since remained available on npm for 1059 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.
v1.2.1
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (walterseymourbc) than the most recent previously approved version (misterben) on 2023-08-16. It has since remained available on npm for 1073 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.
v1.2.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (walterseymourbc) than the most recent previously approved version (misterben) on 2023-08-15. It has since remained available on npm for 1074 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.
v1.1.1
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (awaldron) than the most recent previously approved version (misterben) on 2023-03-31. It has since remained available on npm for 1211 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.
v1.1.0
3 findingsModified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
This version was published by a different npm account (awaldron) than the most recent previously approved version (misterben) on 2023-03-20. It has since remained available on npm for 1222 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.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.