babel-plugin-transform-flow-enums
Babel transform for Flow Enums.
2
Versions
MIT
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
gkzflowtype
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transfer from gkz (Facebook Flow team member) to flowtype org account is a legitimate organizational consolidation; flowtype has 1206 approved packages and strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): flowtype is the official Facebook Flow npm org; adding it as maintainer is expected for this facebook/flow repo package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with org account migration timeline; no code changes and official repo URL confirm legitimate activity. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link style and missing keywords are typical of Facebook OSS packages; not indicative of spam or phishing for this well-known project. | ai |
v0.0.2
2 findings
HIGH
Publisher changed: gkz → flowtype (on 2021-09-13)
provenance
This version was published by a different npm account than previous versions on 2021-09-13. This could indicate a legitimate maintainer transition or an account compromise.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.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.