← Home

@tramvai/plugin-base-builder

4
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

super_olegmeskilltinkoffbank

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): env-spread in server runner worker bridge is expected for a build tool passing env to child workers. ai
semgrep semgrep:child-process-import AI (semgrep): child_process used for self-signed certificate generation — standard build-tool utility. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require resolves babel polyfill definitions at a known absolute path — not arbitrary module loading. ai
semgrep semgrep:eval-usage AI (semgrep): eval() is in an integration test file for polyfill condition evaluation, not production code. ai

Versions (showing 4 of 4)

Version Deps Published
7.20.1 21 / 5
7.17.6 21 / 5
7.16.0 21 / 5
6.80.23 21 / 5

v7.20.1

1 finding
LOW No provenance attestation provenance

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

v7.16.0

3 findings
HIGH env-spread: lib/server-runner/worker-bridge.js:22 semgrep

Spreading entire process.env into an object — may capture all secrets 20 | } 21 | create() { > 22 | const env = { 23 | ...process.env, 24 | HOST: tslib_1.__classPrivateFieldGet(this, _ServerRunnerWorkerBridge_config, "f").host,

HIGH env-spread: src/server-runner/worker-bridge.ts:44 semgrep

Spreading entire process.env into an object — may capture all secrets 42 | 43 | create() { > 44 | const env: Record<string, string | undefined> = { 45 | ...process.env, 46 | HOST: this.#config.host,

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.

v6.80.23

1 finding
LOW No provenance attestation provenance

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