@digitalbazaar/webkms-client
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package; absence of provenance is common and not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 14.3.1 | 5 / 17 | |
| 14.3.0 | 5 / 17 | |
| 14.2.0 | 5 / 17 | |
| 14.1.2 | 5 / 17 | |
| 14.1.1 | 5 / 17 | |
| 14.1.0 | 5 / 17 | |
| 14.0.0 | 5 / 17 |
v14.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dlongley) than the most recent previously approved version (gannan) on 2024-09-19, but dlongley 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.
v14.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.