license-report
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
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 6.8.5 | 11 / 15 | |
| 6.8.2 | 11 / 14 | |
| 6.8.1 | 11 / 14 | |
| 6.8.0 | 11 / 16 | |
| 6.7.2 | 9 / 16 | |
| 6.7.1 | 9 / 16 | |
| 6.7.0 | 9 / 16 |
v6.7.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kessler) than the most recent previously approved version (bepo65) on 2025-03-03, but kessler is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v6.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.