@wyw-in-js/babel-preset
Supply chain provenance
Status for the latest visible version.
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): process.env spread is in a child-process spawn call; standard pattern for passing environment to subprocesses. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval used to deserialize serialized function source in CSS-in-JS tooling; documented and scoped pattern. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publishing with SLSA attestation; consistent with legitimate automation migration for this package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo sub-package; missing description is a known pattern, not a malice indicator here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.0.2 | 3 / 4 | |
| 2.0.1 | 3 / 4 | |
| 2.0.0 | 3 / 4 | |
| 1.1.0 | 2 / 4 | |
| 1.0.8 | 2 / 4 | |
| 1.0.7 | 2 / 4 | |
| 1.0.6 | 2 / 4 | |
| 1.0.5 | 2 / 4 | |
| 1.0.4 | 2 / 4 | |
| 1.0.3 | 2 / 4 | |
| 1.0.2 | 2 / 4 | |
| 1.0.1 | 2 / 4 | |
| 1.0.0 | 2 / 4 | |
| 0.8.1 | 2 / 4 | |
| 0.8.0 | 2 / 4 |
v2.0.2
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/Anber/wyw-in-js/blob/10cbc7ffe66d54978e6f648a812643d0ca28d2d4/esm/index.js#L131 129 | encoding: "utf8", 130 | cwd: payload.root ?? process.cwd(), > 131 | env: { 132 | ...process.env, 133 | NODE_NO_WARNINGS: "1",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Anber/wyw-in-js/blob/10cbc7ffe66d54978e6f648a812643d0ca28d2d4/types/index.js#L148 146 | encoding: 'utf8', 147 | cwd: payload.root ?? process.cwd(), > 148 | env: { 149 | ...process.env, 150 | NODE_NO_WARNINGS: '1',
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.1
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/Anber/wyw-in-js/blob/a981eb7028cc1f324bdc796203cf5d7b62c84476/esm/index.js#L131 129 | encoding: "utf8", 130 | cwd: payload.root ?? process.cwd(), > 131 | env: { 132 | ...process.env, 133 | NODE_NO_WARNINGS: "1",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Anber/wyw-in-js/blob/a981eb7028cc1f324bdc796203cf5d7b62c84476/types/index.js#L148 146 | encoding: 'utf8', 147 | cwd: payload.root ?? process.cwd(), > 148 | env: { 149 | ...process.env, 150 | NODE_NO_WARNINGS: '1',
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
3 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/Anber/wyw-in-js/blob/1603444354fffd7bd28e345224fbd63b2bdbe0bc/esm/index.js#L131 129 | encoding: "utf8", 130 | cwd: payload.root ?? process.cwd(), > 131 | env: { 132 | ...process.env, 133 | NODE_NO_WARNINGS: "1",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/Anber/wyw-in-js/blob/1603444354fffd7bd28e345224fbd63b2bdbe0bc/types/index.js#L148 146 | encoding: 'utf8', 147 | cwd: payload.root ?? process.cwd(), > 148 | env: { 149 | ...process.env, 150 | NODE_NO_WARNINGS: '1',
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.