@didtools/pkh-ethereum
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Stale historical change, publisher has strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old transition, no takeover indicators. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Change is 1072d stale, consistent with legitimate handoff not takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Well-known @noble crypto libs replacing ethersproject deps; normal refactor. | ai | |
| provenance | no-provenance | AI (provenance): Established 3Box Labs / Ceramic Network package; lack of Sigstore provenance is common and not a meaningful risk signal for this package. | ai | |
| dependencies | unvetted-dep:@didtools/cacao | AI (dependencies): @didtools/cacao is a sibling package in the same @didtools namespace from Ceramic Network; a natural and expected dependency for this DID/CACAO Ethereum auth library. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 5 / 1 | |
| 0.5.0 | 5 / 1 | |
| 0.4.1 | 5 / 1 | |
| 0.4.0 | 5 / 1 | |
| 0.3.0 | 5 / 1 | |
| 0.2.1 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.0 | 4 / 1 | |
| 0.0.3 | 4 / 1 | |
| 0.0.2 | 4 / 1 | |
| 0.0.1 | 4 / 1 |
v0.5.0
2 findingsThis version was published by a different npm account (dbcfd) than the most recent previously approved version (zachferland) on 2024-01-04. It has since remained available on npm for 929 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
2 findingsThis version was published by a different npm account (ukstv) than the most recent previously approved version (zachferland) on 2023-08-14. It has since remained available on npm for 1072 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
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 (paul_lecam) than the most recent previously approved version (zachferland) on 2023-02-24, but paul_lecam 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.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.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.