@griffel/babel-preset
Babel preset with build time transforms for Griffel
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is explicitly declared in package.json dependencies; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@linaria/shaker | AI (dependencies): Long-standing beta dep used by this Babel preset; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@linaria/babel-preset | AI (dependencies): Long-standing beta dep used by this Babel preset; stable pattern across versions. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.9.0 | 11 / 0 | |
| 1.8.6 | 11 / 0 | |
| 1.8.5 | 11 / 0 | |
| 1.8.4 | 11 / 0 | |
| 1.8.3 | 11 / 0 | |
| 1.8.2 | 11 / 0 | |
| 1.8.1 | 11 / 0 | |
| 1.8.0 | 11 / 0 | |
| 1.7.0 | 11 / 0 | |
| 1.6.8 | 11 / 0 |
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.