@tramvai/plugin-webpack-builder
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:http-proxy | AI (dependencies): http-proxy is a well-established npm package; its use in a webpack dev-server plugin is expected and benign. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into dev-server worker config is standard; not exfiltration. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is in an integration test file evaluating controlled boolean expressions, not production code. | ai | |
| dependencies | unvetted-dep:svgo | AI (dependencies): svgo is a well-known SVG optimizer; stable legitimate dep for a webpack builder. | ai | |
| dependencies | unvetted-dep:@tinkoff/is-modern-lib | AI (dependencies): First-party @tinkoff dep consistent with tramvai ecosystem; no malware signal. | ai | |
| dependencies | unvetted-dep:@rsdoctor/webpack-plugin | AI (dependencies): rsdoctor is a known webpack analysis tool; legitimate build tooling dep. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Plugin-loader pattern resolving webpack plugins by string name; expected behavior for this builder package. | ai | |
| phantom-deps | phantom-dep:svgo | AI (phantom-deps): svgo is a declared runtime dep used via config/loaders, not direct import; stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo-published internal framework package; missing metadata is typical for this pattern. | ai | |
| phantom-deps | phantom-dep:lightningcss-loader | AI (phantom-deps): lightningcss-loader used via webpack config string references, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:file-loader | AI (phantom-deps): file-loader referenced via webpack config, not direct import; stable false positive. | ai | |
| phantom-deps | phantom-dep:@svgr/webpack | AI (phantom-deps): @svgr/webpack referenced via webpack config, not direct import; stable false positive. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 7.20.2 | 34 / 7 | |
| 7.20.1 | 34 / 7 | |
| 7.19.1 | 34 / 7 | |
| 7.18.0 | 34 / 7 | |
| 7.17.6 | 34 / 7 | |
| 7.17.5 | 34 / 7 | |
| 7.17.2 | 34 / 7 | |
| 7.17.1 | 34 / 7 | |
| 7.16.1 | 34 / 7 | |
| 7.16.0 | 34 / 7 | |
| 7.4.3 | 41 / 9 | |
| 7.2.0 | 41 / 9 | |
| 6.80.23 | 34 / 7 | |
| 6.80.20 | 34 / 7 | |
| 6.80.19 | 34 / 7 | |
| 6.80.16 | 34 / 7 | |
| 6.80.14 | 34 / 7 | |
| 6.80.13 | 34 / 7 | |
| 6.80.11 | 34 / 7 | |
| 6.80.10 | 34 / 7 | |
| 6.80.8 | 34 / 7 | |
| 6.80.7 | 34 / 7 | |
| 6.80.6 | 34 / 7 | |
| 6.79.11 | 41 / 9 | |
| 6.79.0 | 41 / 9 | |
| 6.68.0 | 38 / 9 |
v7.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.3
3 findingsSpreading 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,
Spreading entire process.env into an object — may capture all secrets 40 | 41 | create() { > 42 | const env: Record<string, string | undefined> = { 43 | ...process.env, 44 | HOST: this.#config.host,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
3 findingsSpreading 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,
Spreading entire process.env into an object — may capture all secrets 40 | 41 | create() { > 42 | const env: Record<string, string | undefined> = { 43 | ...process.env, 44 | HOST: this.#config.host,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.80.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.79.11
3 findingsSpreading 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,
Spreading entire process.env into an object — may capture all secrets 40 | 41 | create() { > 42 | const env: Record<string, string | undefined> = { 43 | ...process.env, 44 | HOST: this.#config.host,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.68.0
2 findingsSpreading entire process.env into an object — may capture all secrets 37 | 38 | create() { > 39 | const env: Record<string, string | undefined> = { 40 | ...process.env, 41 | // force color output for worker - https://github.com/chalk/supports-color#info
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.