← Home

@cedarjs/babel-config

Cedar's Babel config. This package has been extracted out of `@cedarjs/internal`.

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

tobbe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@babel/plugin-transform-private-methods AI (phantom-deps): Babel plugin loaded by config convention; stable for this package. ai
phantom-deps phantom-dep:@babel/runtime-corejs3 AI (phantom-deps): Babel runtime loaded by convention in config; stable for this package. ai
phantom-deps phantom-dep:core-js AI (phantom-deps): core-js is a runtime dependency for Babel polyfills; implicit usage is expected. ai
phantom-deps phantom-dep:@babel/plugin-transform-class-properties AI (phantom-deps): Babel plugin loaded by config convention; stable for this package. ai
phantom-deps phantom-dep:@babel/plugin-transform-private-property-in-object AI (phantom-deps): Babel plugin loaded by config convention; stable for this package. ai
bogus-package bogus-package AI (bogus-package): Config package; sparse README and no keywords are normal for internal tooling. ai
provenance no-provenance AI (provenance): Established package with 1433 versions; provenance absence is not a blocker for this context. ai
dependencies unvetted-dep:babel-plugin-graphql-tag AI (dependencies): Known Babel plugin for GraphQL; stable dependency across CedarJS versions, no malware indicators. ai
dependencies unvetted-dep:babel-plugin-auto-import AI (dependencies): Known Babel plugin; stable dependency across CedarJS versions, no malware indicators. ai
phantom-deps phantom-dep:@babel/preset-env AI (phantom-deps): Babel config package references presets by name in config objects, not direct imports — stable false positive. ai
phantom-deps phantom-dep:@babel/plugin-transform-react-jsx AI (phantom-deps): Babel config package references plugins by name in config objects, not direct imports — stable false positive. ai
phantom-deps phantom-dep:@babel/plugin-transform-runtime AI (phantom-deps): Babel config package references plugins by name in config objects, not direct imports — stable false positive. ai
phantom-deps phantom-dep:babel-plugin-graphql-tag AI (phantom-deps): Referenced in config files by plugin name string, not direct import — stable false positive for babel config packages. ai
phantom-deps phantom-dep:babel-plugin-auto-import AI (phantom-deps): Referenced in config files by plugin name string, not direct import — stable false positive for babel config packages. ai
phantom-deps phantom-dep:@babel/preset-typescript AI (phantom-deps): Babel config package references presets by name in config objects, not direct imports — stable false positive. ai
phantom-deps phantom-dep:@babel/preset-react AI (phantom-deps): Babel config package references presets by name in config objects, not direct imports — stable false positive. ai

Versions (showing 7 of 7)

Version Deps Published
4.1.0 16 / 8
4.0.0 16 / 8
3.1.1 16 / 8
2.0.2 21 / 8
2.0.0 21 / 8
1.1.0 21 / 8
1.0.0 21 / 8

v4.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v4.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.

v3.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.

v2.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.