@credo-ts/node
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 publishing with SLSA attestation; legitimate automation for this org-owned package. | ai | |
| phantom-deps | phantom-dep:@2060.io/ffi-napi | AI (phantom-deps): Referenced in config/build files for native FFI binding; not directly imported at runtime is expected for this package. | ai | |
| phantom-deps | phantom-dep:@2060.io/ref-napi | AI (phantom-deps): Same as ffi-napi — config-level reference for native binding; stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @credo-ts/node is unrelated to zod; Levenshtein match is a false positive. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a type-only runtime dep for Express v5; legitimate for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 6 / 4 | |
| 0.6.3 | 6 / 4 | |
| 0.6.2 | 6 / 4 | |
| 0.6.1 | 6 / 4 | |
| 0.6.0 | 8 / 4 | |
| 0.5.19 | 7 / 5 | |
| 0.5.18 | 7 / 5 | |
| 0.5.17 | 7 / 5 | |
| 0.5.16 | 7 / 5 | |
| 0.5.15 | 7 / 5 | |
| 0.5.14 | 7 / 5 |
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. 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.
v0.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.