@credo-ts/drpc
<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 DRPC Module</b
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): Package now published via GitHub Actions CI with SLSA attestation from the official openwallet-foundation org; stable pattern going forward. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer addition consistent with org-level CI/CD transition; SLSA attestation confirms legitimate upstream publishing. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 4 / 3 | |
| 0.6.3 | 4 / 3 | |
| 0.6.2 | 4 / 3 | |
| 0.6.1 | 4 / 3 | |
| 0.6.0 | 4 / 3 | |
| 0.5.19 | 3 / 4 | |
| 0.5.18 | 3 / 4 | |
| 0.5.17 | 3 / 4 | |
| 0.5.16 | 3 / 4 | |
| 0.5.15 | 3 / 4 | |
| 0.5.14 | 3 / 4 |
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. 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.
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.