@tramvai/plugin-babel-transpiler
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in test snapshot loading utility, not runtime code; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-react-constant-elements | AI (phantom-deps): Babel plugin loaded by convention in transpiler config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-nullish-coalescing-operator | AI (phantom-deps): Babel plugin loaded by convention in transpiler config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/preset-react | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/preset-typescript | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@tinkoff/babel-plugin-lodash | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-polyfill-corejs3 | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-define | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-external-helpers | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-runtime | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/cli | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-decorators | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-dynamic-import | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-transform-duplicate-keys | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-numeric-separator | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-optional-chaining | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-object-rest-spread | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-export-default-from | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-react-remove-prop-types | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-dynamic-import-node | AI (phantom-deps): Referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai | |
| phantom-deps | phantom-dep:@babel/register | AI (phantom-deps): Babel plugin package; deps loaded by convention/config, not direct import. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 7.20.3 | 30 / 2 | |
| 7.20.2 | 30 / 2 | |
| 7.20.1 | 30 / 2 | |
| 7.19.1 | 30 / 2 | |
| 7.18.0 | 30 / 2 | |
| 7.17.6 | 30 / 2 | |
| 7.17.5 | 30 / 2 | |
| 7.17.2 | 30 / 2 | |
| 7.17.1 | 30 / 2 | |
| 7.16.1 | 30 / 2 | |
| 7.16.0 | 30 / 2 | |
| 7.11.1 | 28 / 2 | |
| 7.11.0 | 28 / 2 | |
| 7.7.0 | 28 / 2 | |
| 7.5.3 | 28 / 2 | |
| 7.5.1 | 28 / 2 | |
| 7.5.0 | 28 / 2 | |
| 7.4.4 | 28 / 2 | |
| 7.4.3 | 28 / 2 | |
| 7.4.2 | 28 / 2 | |
| 7.4.1 | 28 / 2 | |
| 7.4.0 | 28 / 2 | |
| 7.3.1 | 28 / 2 | |
| 7.3.0 | 28 / 2 | |
| 7.2.3 | 28 / 2 | |
| 7.2.2 | 28 / 2 | |
| 7.2.1 | 28 / 2 | |
| 7.2.0 | 28 / 2 | |
| 7.1.0 | 28 / 2 | |
| 7.0.3 | 28 / 2 | |
| 7.0.2 | 28 / 2 | |
| 7.0.1 | 28 / 2 | |
| 6.80.23 | 30 / 2 | |
| 6.80.22 | 30 / 2 | |
| 6.80.20 | 30 / 2 | |
| 6.80.19 | 30 / 2 | |
| 6.80.16 | 30 / 2 | |
| 6.80.14 | 30 / 2 | |
| 6.80.13 | 30 / 2 | |
| 6.80.11 | 30 / 2 | |
| 6.80.10 | 30 / 2 | |
| 6.80.8 | 30 / 2 | |
| 6.80.7 | 30 / 2 | |
| 6.80.6 | 30 / 2 | |
| 6.79.33 | 28 / 2 | |
| 6.79.24 | 28 / 2 | |
| 6.79.21 | 28 / 2 | |
| 6.79.20 | 28 / 2 | |
| 6.79.19 | 28 / 2 | |
| 6.79.16 | 28 / 2 | |
| 6.79.14 | 28 / 2 |
v7.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.80.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.80.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.80.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.80.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.80.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.80.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.79.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.