metro-transform-worker
🚇 Transform worker 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:metro-babel-transformer | AI (phantom-deps): Loaded dynamically via configurable transformer path; not a static import. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Minimal package.json is a monorepo artifact, not a spam indicator here. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Metro monorepo packages use 0.0.0 placeholder; benign for this trusted package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation via official Facebook GitHub Actions CI mitigates account-takeover concern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Metro intentionally uses dynamic require() to load configurable Babel transformer paths — this is a core design feature of Metro's pluggable transform pipeline, not a security risk. | ai | |
| phantom-deps | phantom-dep:metro-minify-terser | AI (phantom-deps): metro-minify-terser is a sibling monorepo package used via config/dynamic loading; phantom-dep flag is expected for Metro's pluggable architecture. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): flow-enums-runtime is a standard Flow runtime dep in Meta OSS packages; phantom-dep flag is a false positive for this monorepo package pattern. | ai |
Versions (showing 51 of 100)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 13 / 2 | |
| 0.86.0 | 13 / 2 | |
| 0.85.0 | 13 / 2 | |
| 0.84.4 | 13 / 2 | |
| 0.84.3 | 13 / 2 | |
| 0.84.2 | 13 / 2 | |
| 0.84.1 | 13 / 2 | |
| 0.84.0 | 13 / 2 | |
| 0.83.7 | 13 / 2 | |
| 0.83.6 | 13 / 2 | |
| 0.83.5 | 13 / 2 | |
| 0.83.4 | 13 / 2 | |
| 0.83.3 | 13 / 2 | |
| 0.83.2 | 13 / 2 | |
| 0.83.1 | 13 / 2 | |
| 0.83.0 | 13 / 2 | |
| 0.82.5 | 13 / 2 | |
| 0.82.4 | 13 / 2 | |
| 0.82.3 | 13 / 2 | |
| 0.82.2 | 13 / 2 | |
| 0.82.1 | 13 / 2 | |
| 0.82.0 | 13 / 2 | |
| 0.81.5 | 13 / 2 | |
| 0.81.4 | 13 / 2 | |
| 0.81.3 | 13 / 2 | |
| 0.81.2 | 13 / 2 | |
| 0.81.1 | 13 / 2 | |
| 0.81.0 | 13 / 2 | |
| 0.80.12 | 13 / 2 | |
| 0.80.11 | 13 / 2 | |
| 0.80.10 | 13 / 2 | |
| 0.80.9 | 12 / 2 | |
| 0.80.8 | 12 / 2 | |
| 0.80.7 | 12 / 2 | |
| 0.80.6 | 12 / 2 | |
| 0.80.5 | 12 / 2 | |
| 0.80.4 | 11 / 3 | |
| 0.80.3 | 11 / 3 | |
| 0.80.2 | 11 / 3 | |
| 0.80.1 | 11 / 3 | |
| 0.80.0 | 11 / 3 | |
| 0.79.1 | 11 / 3 | |
| 0.79.0 | 11 / 3 | |
| 0.78.1 | 11 / 3 | |
| 0.78.0 | 11 / 3 | |
| 0.77.0 | 12 / 3 | |
| 0.76.9 | 13 / 2 | |
| 0.76.8 | 12 / 3 | |
| 0.76.7 | 12 / 3 | |
| 0.76.6 | 12 / 3 | |
| 0.76.5 | 12 / 3 |
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.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.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.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.
v0.80.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.