@nuggetslife/vc
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 22 of 22)
| 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 |
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
3 findingsSpreading entire process.env into an object — may capture all secrets 62 | '--json', 63 | ], { > 64 | env: { ...process.env, ...p.env, IDV2_JSON: idv2Json }, 65 | encoding: 'utf8', 66 | maxBuffer: 4 * 1024 * 1024,
Spreading entire process.env into an object — may capture all secrets 48 | '--json', 49 | ], { > 50 | env: { ...process.env, ...c.env, BENCH_BACKEND: 'inproc' }, 51 | encoding: 'utf8', 52 | maxBuffer: 8 * 1024 * 1024,
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
3 findingsSpreading entire process.env into an object — may capture all secrets 62 | '--json', 63 | ], { > 64 | env: { ...process.env, ...p.env, IDV2_JSON: idv2Json }, 65 | encoding: 'utf8', 66 | maxBuffer: 4 * 1024 * 1024,
Spreading entire process.env into an object — may capture all secrets 48 | '--json', 49 | ], { > 50 | env: { ...process.env, ...c.env, BENCH_BACKEND: 'inproc' }, 51 | encoding: 'utf8', 52 | maxBuffer: 8 * 1024 * 1024,
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
3 findingsSpreading entire process.env into an object — may capture all secrets 75 | '--json', 76 | ], { > 77 | env: { ...process.env, ...p.env, IDV2_JSON: idv2Json }, 78 | encoding: 'utf8', 79 | maxBuffer: 4 * 1024 * 1024,
Spreading entire process.env into an object — may capture all secrets 54 | '--json', 55 | ], { > 56 | env: { ...process.env, ...c.env, BENCH_BACKEND: 'inproc' }, 57 | encoding: 'utf8', 58 | maxBuffer: 8 * 1024 * 1024,
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
3 findingsSpreading entire process.env into an object — may capture all secrets 75 | '--json', 76 | ], { > 77 | env: { ...process.env, ...p.env, IDV2_JSON: idv2Json }, 78 | encoding: 'utf8', 79 | maxBuffer: 4 * 1024 * 1024,
Spreading entire process.env into an object — may capture all secrets 54 | '--json', 55 | ], { > 56 | env: { ...process.env, ...c.env, BENCH_BACKEND: 'inproc' }, 57 | encoding: 'utf8', 58 | maxBuffer: 8 * 1024 * 1024,
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.