← Home

babel-plugin-transform-conditionals

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

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

boopathi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Package is ~10 years old from a trusted publisher (boopathi) with 623 approved packages. The 0.0.0 version is a legitimate early placeholder, not a malware indicator. ai
bogus-package bogus-package AI (bogus-package): Sparse metadata is consistent with an old placeholder Babel plugin from a well-established, trusted publisher. No malicious signals present. ai

Versions (showing 4 of 4)

Version Deps Published
0.1.2 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0
0.0.0 0 / 0

v0.1.2

1 finding
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.1.1

1 finding
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.1.0

1 finding
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.0.0

1 finding
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.