← Home

@terminal3/verify_vc

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 scoped package in an established org; missing metadata is consistent across all versions, not a spam indicator. ai
phantom-deps phantom-dep:ethers AI (phantom-deps): Likely re-exported or used indirectly via @terminal3 sub-packages; stable false positive for this package. ai
phantom-deps phantom-dep:did-jwt AI (phantom-deps): Same pattern as ethers — indirect use via internal deps; stable false positive. ai
phantom-deps phantom-dep:@noble/curves AI (phantom-deps): Cryptographic primitive likely consumed by @terminal3/bbs_vc or ecdsa_vc; stable false positive. ai

Versions (showing 12 of 12)

Version Deps Published
0.0.38 6 / 1
0.0.37 6 / 1
0.0.35 6 / 1
0.0.34 6 / 1
0.0.33 6 / 1
0.0.32 6 / 1
0.0.31 6 / 1
0.0.30 6 / 1
0.0.29 6 / 1
0.0.28 6 / 1
0.0.27 6 / 1
0.0.26 6 / 1

v0.0.38

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

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: trha → phuc-t3 (on 2026-05-06, known maintainer) provenance

This version was published by a different npm account (phuc-t3) than the most recent previously approved version (trha) on 2026-05-06, but phuc-t3 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.35

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: trha → phuc-t3 (on 2026-04-24, known maintainer) provenance

This version was published by a different npm account (phuc-t3) than the most recent previously approved version (trha) on 2026-04-24, but phuc-t3 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.34

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.33

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

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

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: phuc-t3 → trha (on 2025-11-13, known maintainer) provenance

This version was published by a different npm account (trha) than the most recent previously approved version (phuc-t3) on 2025-11-13, but trha is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.30

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: phuc-t3 → trha (on 2025-10-28, known maintainer) provenance

This version was published by a different npm account (trha) than the most recent previously approved version (phuc-t3) on 2025-10-28, but trha is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.29

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: phuc-t3 → nik-t3 (on 2025-09-05, known maintainer) provenance

This version was published by a different npm account (nik-t3) than the most recent previously approved version (phuc-t3) on 2025-09-05, but nik-t3 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.0.28

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: phuc-t3 → nik-t3 (on 2025-09-05, known maintainer) provenance

This version was published by a different npm account (nik-t3) than the most recent previously approved version (phuc-t3) on 2025-09-05, but nik-t3 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

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.