@credo-ts/anoncreds
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing backed by SLSA provenance attestation; consistent with openwallet-foundation org practices. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer genaris added alongside CI/CD transition in established openwallet-foundation org; not indicative of compromise. | ai | |
| phantom-deps | phantom-dep:@sphereon/pex-models | AI (phantom-deps): Declared dep used in config/type references rather than direct imports; stable false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 7 / 5 | |
| 0.6.3 | 7 / 5 | |
| 0.6.2 | 7 / 5 | |
| 0.6.1 | 7 / 5 | |
| 0.6.0 | 7 / 5 | |
| 0.5.19 | 8 / 6 | |
| 0.5.18 | 8 / 6 | |
| 0.5.17 | 8 / 6 | |
| 0.5.16 | 8 / 6 | |
| 0.5.15 | 8 / 6 | |
| 0.5.14 | 8 / 6 |
v0.6.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.