babel-plugin-formatjs No license 28 versions

babel-plugin-formatjs

npm Repository Homepage

28

Versions

—

License

No

Install Scripts

Verified

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pyrocatlonglho

Keywords

babel-pluginreact-intl

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher is GitHub Actions with SLSA attestation; formatjs migrated to CI publishing — stable pattern for this package.	ai	2026/04/30
publish-pattern	dormant-publish	AI (publish-pattern): Major version bump in active monorepo; dormancy reflects development cycle, not abandonment or takeover.	ai	2026/04/30
phantom-deps	phantom-dep:@babel/traverse	AI (phantom-deps): Framework-scoped Babel peer dep; loaded by convention in babel plugin ecosystem.	ai	2026/04/30
phantom-deps	phantom-dep:@types/babel__core	AI (phantom-deps): TypeScript @types package loaded by convention, not directly imported — stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@types/babel__traverse	AI (phantom-deps): TypeScript @types package loaded by convention, not directly imported — stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@types/babel__helper-plugin-utils	AI (phantom-deps): TypeScript @types package loaded by convention, not directly imported — stable false positive for this package.	ai	2026/04/29

Versions (showing 28 of 28)

Version	Deps	Published
11.3.10	10 / 0	2026-05-27
11.3.9	10 / 0	2026-05-22
11.3.8	10 / 0	2026-05-15
11.3.7	10 / 0	2026-05-12
11.3.6	10 / 0	2026-05-05
11.3.5	10 / 0	2026-04-29
11.3.4	10 / 0	2026-04-24
11.3.3	10 / 0	2026-04-13
11.3.2	10 / 0	2026-03-27
11.3.1	10 / 0	2026-03-19
11.3.0	10 / 0	2026-03-17
11.2.5	10 / 0	2026-03-16
11.2.4	11 / 0	2026-02-19
11.2.3	11 / 0	2026-02-03
11.2.2	11 / 0	2026-02-01
11.2.1	11 / 0	2026-01-19
11.2.0	11 / 0	2026-01-15
11.1.1	11 / 0	2026-01-06
11.1.0	11 / 0	2026-01-02
11.0.8	11 / 0	2025-12-28
11.0.7	11 / 0	2025-12-26
11.0.6	11 / 0	2025-12-23
11.0.5	11 / 0	2025-12-23
11.0.4	11 / 0	2025-12-19
11.0.2	11 / 0	2025-12-17
11.0.1	11 / 0	2025-12-15
11.0.0	11 / 0	2025-12-15
10.5.36	11 / 0	2025-03-23

v11.3.10

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.9

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.8

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.7

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.6

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.5

2 findings

HIGH Publisher changed: longlho → GitHub Actions (on 2026-04-29) provenance

This version was published by a different npm account than previous versions on 2026-04-29. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.4

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.3

2 findings

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: longlho → GitHub Actions (on 2026-04-13) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-04-13. This could indicate a legitimate maintainer transition or an account compromise.

v11.3.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.3.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.2.5

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.2.4

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.2.3

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.2.2

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.2.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.2.0

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.1.1

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v11.1.0

2 findings

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: longlho → GitHub Actions (on 2026-01-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-02. This could indicate a legitimate maintainer transition or an account compromise.

v11.0.8

1 finding

LOW No provenance attestation provenance

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

v11.0.7

1 finding

LOW No provenance attestation provenance

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

v11.0.6

1 finding

LOW No provenance attestation provenance

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

v11.0.5

1 finding

LOW No provenance attestation provenance

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

v11.0.4

1 finding

LOW No provenance attestation provenance

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

v11.0.2

1 finding

LOW No provenance attestation provenance

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

v11.0.1

1 finding

LOW No provenance attestation provenance

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

v11.0.0

1 finding

LOW No provenance attestation provenance

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

v10.5.36

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.