@sc-voice/ms-dpd
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tmp | AI (phantom-deps): tmp is a declared runtime dependency; phantom-dep heuristic fires because it may not be directly imported in scanned files. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.54.0 | 7 / 8 | |
| 2.8.0 | 1 / 4 | |
| 2.7.0 | 1 / 4 | |
| 2.5.0 | 1 / 4 | |
| 2.4.0 | 1 / 4 |
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.