meteor-babel
Babel wrapper package for use with Meteor
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 | publisher-changed | AI (provenance): Transition from benjamn to mdg is the Meteor org account; legitimate org-level handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): filipenevola is a known Meteor contributor; addition consistent with org transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org-level maintainer transition; not indicative of takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): typescript added as direct dep replacing @babel/plugin-transform-typescript; functionally equivalent swap. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Cache file loading pattern in a Babel wrapper; not user-controlled arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): Framework-scoped Babel package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/types | AI (phantom-deps): Framework-scoped Babel package loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/parser | AI (phantom-deps): Framework-scoped Babel package loaded by convention; stable false positive for this package. | ai |
v7.10.7
2 findingsThis version was published by a different npm account than previous versions on 2021-03-18. 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.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.