← Home

@terminal3/verify_vc_core

npm
12
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

nik-t3edward-fu-t3matthew-t3jeff-t3phuc-t3trha

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): Internal org package; missing metadata is consistent across all @terminal3/* packages, not a spam/malware indicator. ai
npm-metadata no-description AI (npm-metadata): Stable pattern across this org's packages; not indicative of malice. ai
phantom-deps phantom-dep:ethers AI (phantom-deps): Declared in package.json dependencies; heuristic false positive for this package. ai
phantom-deps phantom-dep:did-jwt AI (phantom-deps): Declared in package.json dependencies; heuristic false positive for this package. ai
phantom-deps phantom-dep:@noble/curves AI (phantom-deps): Declared in package.json dependencies; heuristic false positive for this package. ai

Versions (showing 12 of 12)

Version Deps Published
0.0.37 5 / 0
0.0.36 5 / 0
0.0.34 5 / 0
0.0.33 5 / 0
0.0.32 5 / 0
0.0.31 5 / 0
0.0.30 5 / 0
0.0.29 5 / 0
0.0.28 5 / 0
0.0.27 5 / 0
0.0.26 5 / 0
0.0.25 5 / 0

v0.0.37

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.

v0.0.36

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.

v0.0.34

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.

v0.0.33

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.

v0.0.32

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.

v0.0.31

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.

v0.0.30

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.

v0.0.29

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.

v0.0.28

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.

v0.0.27

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.

v0.0.26

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.

v0.0.25

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.