@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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): rxjs is a mainstream, widely-used reactive library; not a plausible exfil vector. | ai | |
| provenance | missing-githead | AI (provenance): Metadata gap only, no behavioral change; org has strong track record. | ai | |
| 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/ref-napi | AI (phantom-deps): Same as ffi-napi — config-level reference for native binding; stable pattern for this 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 | |
| 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 25 of 25)
| 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 | |
| 0.5.13 | 7 / 5 | |
| 0.5.12 | 7 / 5 | |
| 0.5.11 | 6 / 5 | |
| 0.5.10 | 6 / 5 | |
| 0.5.9 | 6 / 5 | |
| 0.5.8 | 6 / 5 | |
| 0.5.7 | 6 / 5 | |
| 0.5.6 | 6 / 5 | |
| 0.5.5 | 6 / 5 | |
| 0.5.4 | 6 / 5 | |
| 0.5.3 | 6 / 5 | |
| 0.5.2 | 6 / 5 | |
| 0.5.1 | 6 / 5 | |
| 0.5.0 | 6 / 5 |
v0.5.13
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: openwalletfoundation.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.