@digitalbazaar/data-integrity
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Signal is from co-maintainer mattcollier's package count; @digitalbazaar/data-integrity is a legitimate cryptographic library, not spam. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.5.0 | 3 / 22 | |
| 2.4.0 | 3 / 22 | |
| 2.3.0 | 3 / 22 | |
| 2.2.0 | 3 / 22 | |
| 2.1.0 | 3 / 22 | |
| 2.0.0 | 3 / 22 |
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.