← Home

@digitalcredentials/vc

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

codenamedmitrikimhduligallalexander.muehlestuartfjchartrandkiliankaeklemoiekezike

Keywords

JSONLinked DataJSON-LDRDFSemantic WebVerifiable ClaimCredential

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @digitalcredentials/vc cannot be a typosquat of unscoped 'pg'; edit-distance match is meaningless here. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @digitalcredentials/vc cannot be a typosquat of unscoped 'qs'; edit-distance match is meaningless here. ai
phantom-deps phantom-dep:ed25519-signature-2018-context AI (phantom-deps): Context package used in JSON-LD context loading config, not direct ES imports; stable false positive for this package. ai

Versions (showing 3 of 3)

Version Deps Published
10.0.2 6 / 33
10.0.1 6 / 33
10.0.0 6 / 33

v10.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.