← Home

@nuggetslife/vc

npm
31
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

alastairjab-cialordlloydasamoah88emmanuelnuggetssamnuggetsmartinnuggetsharry-anderson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Fires in bench/frame_compare.mjs benchmark script, not runtime library code. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @nuggetslife/vc; not a typosquat of qs — different namespace and purpose. ai
semgrep semgrep:child-process-execsync AI (semgrep): Standard napi-rs musl detection pattern using 'which ldd'; not arbitrary code execution. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @nuggetslife/vc; not a typosquat of pg — different namespace and purpose. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding in BBS+ cryptographic demo/test files; expected for a VC crypto library. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decoding in BBS+ test files for commitment/proof bytes; expected crypto usage. ai
semgrep semgrep:child-process-import AI (semgrep): Same musl detection pattern; benign for napi-rs native binding loader. ai

Versions (showing 31 of 31)

Version Deps Published
0.4.1 0 / 6
0.4.0 0 / 6
0.3.2 0 / 6
0.3.1 0 / 6
0.3.0 0 / 6
0.2.0 0 / 6
0.1.0 0 / 5
0.0.30 0 / 5
0.0.29 0 / 5
0.0.28 0 / 5
0.0.27 0 / 5
0.0.26 0 / 5
0.0.25 0 / 5
0.0.24 0 / 5
0.0.23 0 / 5
0.0.21 0 / 5
0.0.20 0 / 5
0.0.19 0 / 5
0.0.18 0 / 5
0.0.17 0 / 5
0.0.16 0 / 5
0.0.15 0 / 5
0.0.10 0 / 4
0.0.9 0 / 6
0.0.8 0 / 6
0.0.7 0 / 6
0.0.6 0 / 6
0.0.5 0 / 6
0.0.4 0 / 6
0.0.3 0 / 4
0.0.2 0 / 4

v0.0.10

1 finding
LOW No provenance attestation provenance

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

v0.0.9

1 finding
LOW No provenance attestation provenance

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

v0.0.8

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

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