← Home

@formatjs/cli

npm Repository Homepage
40
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

longlhoredonkuluspyrocat

Keywords

cliformatformatjsformattingglobalizationi18ninternationalizationintllocalelocalizationreactreact-intlreactjstranslatetranslation

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Move to GitHub Actions CI/CD publishing with SLSA attestation; benign transition for this package. ai
source-diff obfuscated-file:bin/parse_script-3um9mN8Y.js AI (source-diff): Bundled CLI binary (rolldown output); long lines are minified bundle, not obfuscation. ai
source-diff net-exec-file:bin/parse_script-3um9mN8Y.js AI (source-diff): Network+exec pattern in a CLI tool bundle is expected; no dropper indicators in the sample. ai
source-diff obfuscated-file:bin/parse_script-Dh6HQV8l.js AI (source-diff): Rolldown-bundled CLI artifact; long lines are minified bundle output, not obfuscation. Stable pattern for this package. ai
source-diff net-exec-file:bin/parse_script-Dh6HQV8l.js AI (source-diff): CLI tool legitimately makes network calls (e.g. fetching translations) and uses dynamic requires in bundled output; no dropper pattern visible. ai
typosquat typosquat.levenshtein:joi AI (typosquat): @formatjs/cli is a well-established i18n CLI tool, not a typosquat of joi; Levenshtein match is spurious. ai

Versions (showing 40 of 40)

Version Deps Published
6.16.14 0 / 0
6.16.13 0 / 0
6.16.12 0 / 0
6.16.11 0 / 0
6.16.10 0 / 0
6.16.9 0 / 0
6.16.8 0 / 0
6.16.7 0 / 0
6.16.6 0 / 1
6.16.5 0 / 1
6.16.3 0 / 1
6.16.2 0 / 1
6.16.1 0 / 1
6.16.0 0 / 1
6.15.0 0 / 1
6.14.5 0 / 1
6.14.4 0 / 1
6.14.3 0 / 1
6.14.2 0 / 1
6.14.1 0 / 1
6.14.0 0 / 1
6.13.4 0 / 1
6.13.3 0 / 1
6.13.2 0 / 1
6.13.1 0 / 1
6.13.0 0 / 1
6.12.2 0 / 1
6.12.1 0 / 1
6.12.0 0 / 1
6.11.0 0 / 1
6.10.0 0 / 1
6.9.0 0 / 1
6.8.8 0 / 1
6.8.7 0 / 1
6.8.6 0 / 1
6.8.5 0 / 1
6.8.4 0 / 1
6.8.2 0 / 1
6.8.1 0 / 1
6.8.0 0 / 1

v6.16.14

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.

v6.16.13

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.

v6.16.12

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.

v6.16.11

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.

v6.14.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.

v6.14.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.

v6.13.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.

v6.13.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.

v6.13.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.

v6.13.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.

v6.13.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.

v6.12.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.

v6.12.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.

v6.12.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.

v6.11.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.

v6.10.0

2 findings
HIGH Publisher changed: longlho → GitHub Actions (on 2026-01-06) provenance

This version was published by a different npm account than previous versions on 2026-01-06. 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.

v6.9.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, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (longlho) on 2026-01-02, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v6.8.8

1 finding
LOW No provenance attestation provenance

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

v6.8.7

1 finding
LOW No provenance attestation provenance

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

v6.8.6

1 finding
LOW No provenance attestation provenance

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

v6.8.5

1 finding
LOW No provenance attestation provenance

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

v6.8.4

1 finding
LOW No provenance attestation provenance

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

v6.8.2

1 finding
LOW No provenance attestation provenance

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

v6.8.1

1 finding
LOW No provenance attestation provenance

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

v6.8.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.