@vibe-forge/benchmark — Greenflagged

Benchmark discovery and execution for Vibe Forge

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yijie4188nirvana30

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:env-spread	AI (semgrep): Idiomatic child-process env construction; spreading process.env as base before selective overrides is standard and not a data-exfiltration risk here.	ai	2026/05/26

Versions (showing 2 of 2)

Version	Deps	Published
3.3.1	6 / 0	2026-05-16
0.8.3	5 / 0	2026-03-31

v3.3.1

2 findings

HIGH env-spread: src/utils.ts:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | 54 | return new Promise((resolve, reject) => { > 55 | const childEnv: NodeJS.ProcessEnv = { ...process.env } 56 | for (const [key, value] of Object.entries(env ?? {})) { 57 | if (value != null) {

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

2 findings

HIGH env-spread: src/utils.ts:55 semgrep

Spreading entire process.env into an object — may capture all secrets 53 | 54 | return new Promise((resolve, reject) => { > 55 | const childEnv: NodeJS.ProcessEnv = { ...process.env } 56 | for (const [key, value] of Object.entries(env ?? {})) { 57 | if (value != null) {

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.