@credo-ts/hedera
<p align="center"> <br /> <img alt="Credo Logo" src="https://github.com/openwallet-foundation/credo-ts/blob/c7886cb8377ceb8ee4efe8d264211e561a75072d/images/credo-logo.png" height="250px" /> </p> <h1 align="center"><b>Credo Hedera Module<
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): genaris is a known credo-ts contributor; legitimate maintainer addition. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate CI/CD migration from manual npm publish to GitHub Actions with SLSA provenance. | ai | |
| provenance | slsa-provenance | AI (provenance): SLSA attestation confirms CI/CD provenance; positive signal. | ai | |
| dependencies | unvetted-dep:@hiero-did-sdk/resolver | AI (dependencies): Legitimate Hedera DID SDK dependency expected for this package's DID resolution functionality. | ai | |
| dependencies | unvetted-dep:@hiero-did-sdk/registrar | AI (dependencies): Legitimate Hedera DID SDK dependency expected for this package's DID registration functionality. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 12 / 3 | |
| 0.6.3 | 11 / 3 | |
| 0.6.2 | 11 / 3 | |
| 0.6.1 | 11 / 3 | |
| 0.6.0 | 11 / 3 | |
| 0.5.19 | 11 / 4 | |
| 0.5.18 | 11 / 4 |
v0.7.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-29. 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.3
2 findingsThis version was published by a different npm account than previous versions on 2026-03-09. 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.2
1 findingPublished 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.