babel-plugin-dev-expression
A mirror of Facebook's dev-expression Babel plugin
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 92k weekly downloads and long history; lack of Sigstore provenance is a process gap, not a security indicator for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from taion to monastic.panic reflects a legitimate 4Catalyzer org maintainer transition; monastic.panic has a strong track record (3987 approved, 0 rejected). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer monastic.panic is a well-established publisher; addition is consistent with a legitimate org-level handoff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a no-content-change release is consistent with a maintainer transition, not a takeover. No code changes were introduced. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.3 | 0 / 4 | |
| 0.2.2 | 0 / 2 | |
| 0.2.1 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.0 | 0 / 0 |
v0.2.3
2 findingsThis version was published by a different npm account than previous versions on 2021-10-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: taion.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.