@credo-ts/core
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:ec-compression | AI (dependencies): Small EC compression utility; consistent with credo-ts crypto scope and no malicious indicators. | ai | |
| phantom-deps | phantom-dep:@multiformats/base-x | AI (phantom-deps): Declared as a dependency for transitive/config use; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@sd-jwt/types | AI (phantom-deps): Type-only package used via config/tsconfig, not direct imports. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @credo-ts/core is an established SSI framework; no plausible impersonation of 'cors'. | ai | |
| phantom-deps | phantom-dep:@sd-jwt/jwt-status-list | AI (phantom-deps): Referenced in config files; stable false positive for this SSI framework. | ai | |
| phantom-deps | phantom-dep:@sd-jwt/utils | AI (phantom-deps): Utility types referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/ws | AI (phantom-deps): Type-only dependency; not directly imported at runtime by design. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 43 / 6 | |
| 0.6.3 | 42 / 6 | |
| 0.6.1 | 42 / 6 | |
| 0.6.0 | 42 / 6 | |
| 0.5.19 | 41 / 9 | |
| 0.5.18 | 41 / 9 | |
| 0.5.17 | 42 / 9 | |
| 0.5.16 | 42 / 9 | |
| 0.5.15 | 42 / 9 | |
| 0.5.14 | 42 / 9 |
v0.6.3
2 findingsPackage name '@credo-ts/core' is 1 edit(s) away from popular package 'cors'.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.