metro-minify-terser MIT 21 versions

metro-minify-terser

npm Repository Homepage

🚇 Minifier for Metro based on Terser.

21

Versions

MIT

License

No

Install Scripts

Attested

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

fbmetro-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed-stale	AI (provenance): Same stale historical publisher change, long-since settled, no unpublish.	ai	2026/07/19
maintainer-change	maintainer-takeover	AI (maintainer-change): Long-lived official facebook/metro package; consistent org maintainer shift, not a compromise.	ai	2026/07/19
provenance	publisher-changed	AI (provenance): Legitimate CI migration from metro-bot to GitHub Actions with SLSA provenance; facebook/metro monorepo.	ai	2026/04/28
publish-pattern	dormant-publish	AI (publish-pattern): Monorepo release cadence; 8.3M downloads, SLSA-attested, facebook/metro org.	ai	2026/04/28
phantom-deps	phantom-dep:flow-enums-runtime	AI (phantom-deps): Flow runtime dep injected by transpiler; standard for Meta packages.	ai	2026/04/28

Versions (showing 21 of 121)

Version	Deps	Published
0.55.0	1 / 0	2019-07-04
0.54.1	1 / 0	2019-05-14
0.54.0	1 / 0	2019-05-01
0.53.1	1 / 0	2019-03-14
0.53.0	1 / 0	2019-03-01
0.52.0	1 / 0	2019-02-19
0.51.1	1 / 0	2018-12-21
0.51.0	1 / 0	2018-12-18
0.50.0	1 / 0	2018-11-29
0.49.2	1 / 0	2018-11-15
0.49.1	1 / 0	2018-11-12
0.49.0	1 / 0	2018-10-30
0.48.5	1 / 0	2018-12-12
0.48.4	1 / 0	2018-12-12
0.48.3	1 / 0	2018-10-29
0.48.2	1 / 0	2018-10-27
0.48.1	1 / 0	2018-10-10
0.48.0	1 / 0	2018-10-05
0.47.1	1 / 0	2018-10-04
0.47.0	1 / 0	2018-09-27
0.46.0	1 / 0	2018-09-24

v0.55.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.54.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.54.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.53.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.53.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.52.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.51.1

2 findings

MEDIUM Publisher changed: rafeca → metro-bot (on 2018-12-21, unremoved on npm for 2766d) provenance

This version was published by a different npm account (metro-bot) than the most recent previously approved version (rafeca) on 2018-12-21. It has since remained available on npm for 2766 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.51.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.50.0

2 findings

MEDIUM Publisher changed: rafeca → metro-bot (on 2018-11-29, unremoved on npm for 2788d) provenance

This version was published by a different npm account (metro-bot) than the most recent previously approved version (rafeca) on 2018-11-29. It has since remained available on npm for 2788 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.49.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.49.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.49.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.48.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.48.4

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: metro-bot → rafeca (on 2018-12-12, known maintainer) provenance

This version was published by a different npm account (rafeca) than the most recent previously approved version (metro-bot) on 2018-12-12, but rafeca is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.48.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.48.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.48.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.48.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.47.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.47.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.46.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.