metro-babel-register
🚇 babel/register configuration for Metro.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Metro monorepo package with long release history; dormancy flag is a false positive for this well-known package. | ai | |
| dependencies | unvetted-dep:babel-plugin-replace-ts-export-assignment | AI (dependencies): Long-standing dependency in this package; stable across versions with no malicious signals. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Loaded by @babel/register convention, not directly imported; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): Runtime peer used by babel-plugin-transform-flow-enums config; not directly imported by design. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 11 / 0 | |
| 0.86.0 | 11 / 0 | |
| 0.85.0 | 11 / 0 | |
| 0.84.4 | 11 / 0 | |
| 0.84.3 | 11 / 0 | |
| 0.84.2 | 11 / 0 | |
| 0.84.1 | 11 / 0 | |
| 0.84.0 | 11 / 0 | |
| 0.83.7 | 11 / 0 | |
| 0.83.6 | 11 / 0 | |
| 0.83.5 | 11 / 0 | |
| 0.83.4 | 11 / 0 | |
| 0.83.3 | 11 / 0 | |
| 0.83.2 | 11 / 0 | |
| 0.83.1 | 11 / 0 | |
| 0.83.0 | 11 / 0 | |
| 0.82.5 | 11 / 0 | |
| 0.82.4 | 11 / 0 | |
| 0.82.3 | 11 / 0 | |
| 0.82.2 | 11 / 0 | |
| 0.82.1 | 11 / 0 | |
| 0.82.0 | 11 / 0 | |
| 0.81.5 | 11 / 0 | |
| 0.81.4 | 11 / 0 | |
| 0.81.3 | 11 / 0 | |
| 0.81.2 | 11 / 0 | |
| 0.81.1 | 11 / 0 | |
| 0.81.0 | 11 / 0 | |
| 0.80.12 | 11 / 0 | |
| 0.80.11 | 11 / 0 | |
| 0.80.10 | 11 / 0 | |
| 0.80.9 | 10 / 0 |
v0.87.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.86.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.84.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.83.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.81.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.