metro-file-map
[Experimental] - 🚇 File crawling, watching and mapping 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:jest-serializer | AI (phantom-deps): Sibling Jest ecosystem package; expected dep. | ai | |
| phantom-deps | phantom-dep:jest-util | AI (phantom-deps): Sibling Jest ecosystem package; expected dep. | ai | |
| phantom-deps | phantom-dep:micromatch | AI (phantom-deps): Standard glob-matching dep; false positive on scan. | ai | |
| phantom-deps | phantom-dep:fb-watchman | AI (phantom-deps): Facebook watchman client, core to file watching functionality. | ai | |
| phantom-deps | phantom-dep:graceful-fs | AI (phantom-deps): Common fs wrapper dep, widely used. | ai | |
| phantom-deps | phantom-dep:jest-worker | AI (phantom-deps): Sibling Jest ecosystem package; expected dep. | ai | |
| phantom-deps | phantom-dep:jest-regex-util | AI (phantom-deps): Sibling Jest ecosystem package; expected dep. | ai | |
| phantom-deps | phantom-dep:walker | AI (phantom-deps): Standard file-crawling dep for metro-file-map; likely used dynamically. | ai | |
| phantom-deps | phantom-dep:anymatch | AI (phantom-deps): Standard glob-matching dep; false positive on scan. | ai | |
| phantom-deps | phantom-dep:invariant | AI (phantom-deps): Common Facebook utility lib, widely used across their packages. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from metro-bot to GitHub Actions is consistent with CI/CD automation; SLSA attestation confirms integrity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by monorepo release cadence; SLSA provenance and no code changes confirm legitimate publish. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used in Metro's plugin system to load user-configured dependency extractors — a standard extensibility pattern for a bundler tool. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Sparse README and missing keywords are cosmetic issues typical of monorepo sub-packages from large orgs like Meta; not a security signal. | ai | |
| phantom-deps | phantom-dep:flow-enums-runtime | AI (phantom-deps): flow-enums-runtime is declared in package.json dependencies; used by Flow-typed code in Meta's packages, not directly imported in compiled JS output. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Metro file-map is a filesystem crawler/bundler tool; child_process usage for native 'find' command support is documented and expected behavior for this package. | ai |
Versions (showing 80 of 80)
| Version | Deps | Published |
|---|---|---|
| 0.87.0 | 9 / 1 | |
| 0.86.0 | 9 / 1 | |
| 0.85.0 | 9 / 1 | |
| 0.84.4 | 9 / 1 | |
| 0.84.3 | 9 / 1 | |
| 0.84.2 | 9 / 1 | |
| 0.84.1 | 9 / 1 | |
| 0.84.0 | 9 / 1 | |
| 0.83.7 | 9 / 1 | |
| 0.83.6 | 9 / 1 | |
| 0.83.5 | 9 / 1 | |
| 0.83.4 | 9 / 1 | |
| 0.83.3 | 9 / 1 | |
| 0.83.2 | 9 / 1 | |
| 0.83.1 | 9 / 1 | |
| 0.83.0 | 9 / 1 | |
| 0.82.5 | 9 / 1 | |
| 0.82.4 | 9 / 1 | |
| 0.82.3 | 9 / 1 | |
| 0.82.2 | 9 / 1 | |
| 0.82.1 | 9 / 1 | |
| 0.82.0 | 9 / 1 | |
| 0.81.5 | 9 / 1 | |
| 0.81.4 | 9 / 1 | |
| 0.81.3 | 9 / 1 | |
| 0.81.2 | 9 / 1 | |
| 0.81.1 | 9 / 1 | |
| 0.81.0 | 11 / 1 | |
| 0.80.12 | 11 / 1 | |
| 0.80.11 | 11 / 1 | |
| 0.80.10 | 12 / 1 | |
| 0.80.9 | 11 / 1 | |
| 0.80.8 | 11 / 1 | |
| 0.80.7 | 11 / 1 | |
| 0.80.6 | 11 / 1 | |
| 0.80.5 | 11 / 1 | |
| 0.80.4 | 11 / 1 | |
| 0.80.3 | 11 / 1 | |
| 0.80.2 | 11 / 1 | |
| 0.80.1 | 11 / 1 | |
| 0.80.0 | 11 / 1 | |
| 0.79.1 | 12 / 1 | |
| 0.79.0 | 12 / 1 | |
| 0.78.1 | 12 / 1 | |
| 0.78.0 | 12 / 1 | |
| 0.77.0 | 13 / 1 | |
| 0.76.9 | 13 / 1 | |
| 0.76.8 | 13 / 1 | |
| 0.76.7 | 13 / 1 | |
| 0.76.6 | 13 / 1 | |
| 0.76.5 | 13 / 1 | |
| 0.76.4 | 13 / 1 | |
| 0.76.3 | 13 / 1 | |
| 0.76.2 | 13 / 1 | |
| 0.76.1 | 13 / 1 | |
| 0.76.0 | 14 / 1 | |
| 0.75.1 | 14 / 1 | |
| 0.75.0 | 14 / 1 | |
| 0.74.1 | 14 / 1 | |
| 0.74.0 | 14 / 1 | |
| 0.73.10 | 14 / 1 | |
| 0.73.9 | 14 / 1 | |
| 0.73.8 | 14 / 1 | |
| 0.73.7 | 14 / 1 | |
| 0.73.6 | 14 / 1 | |
| 0.73.5 | 14 / 1 | |
| 0.73.4 | 14 / 1 | |
| 0.73.3 | 14 / 1 | |
| 0.73.2 | 13 / 1 | |
| 0.73.1 | 13 / 1 | |
| 0.73.0 | 13 / 1 | |
| 0.72.3 | 13 / 1 | |
| 0.72.2 | 13 / 1 | |
| 0.72.1 | 13 / 1 | |
| 0.72.0 | 13 / 1 | |
| 0.71.3 | 13 / 1 | |
| 0.71.2 | 12 / 1 | |
| 0.71.1 | 11 / 1 | |
| 0.71.0 | 11 / 1 | |
| 0.70.1 | 10 / 1 |
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.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.
v0.76.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.