← Home

@credo-ts/core

11
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

openwalletfoundationtimoglastragenaris

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from manual publish to GitHub Actions CI/CD with SLSA provenance; expected for this org. ai
maintainer-change maintainer-added AI (maintainer-change): genaris is a known contributor to the openwallet-foundation/credo-ts project. ai
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
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:@types/ws AI (phantom-deps): Type-only dependency; not directly imported at runtime by design. ai
phantom-deps phantom-dep:@sd-jwt/types AI (phantom-deps): Type-only package used via config/tsconfig, not direct imports. ai
phantom-deps phantom-dep:@sd-jwt/utils AI (phantom-deps): Utility types referenced in config files; stable false positive for this package. ai

Versions (showing 11 of 11)

Version Deps Published
0.7.0 43 / 6
0.6.3 42 / 6
0.6.2 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.2

2 findings
HIGH Publisher changed: openwalletfoundation → GitHub Actions (on 2026-02-04) provenance

This 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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.