← Home

@freckle/i18n-scripts

npm Repository Homepage

Scripts for i18n

9
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

luckysonifreckle-engineeringcarlos-cubasstackptrz0isch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established Freckle org package; lack of provenance is common and not a risk signal here. ai
phantom-deps phantom-dep:i18next AI (phantom-deps): CLI tool lists i18next as a runtime dep for consumers; not directly imported in scripts themselves. ai
phantom-deps phantom-dep:i18next-icu AI (phantom-deps): Same pattern — peer/consumer dep, not directly imported in CLI scripts. ai
phantom-deps phantom-dep:intl-messageformat AI (phantom-deps): Same pattern — peer/consumer dep, not directly imported in CLI scripts. ai
phantom-deps phantom-dep:i18next-http-backend AI (phantom-deps): Same pattern — peer/consumer dep, not directly imported in CLI scripts. ai

Versions (showing 9 of 9)

Version Deps Published
1.1.10 6 / 0
1.1.9 6 / 0
1.1.8 6 / 0
1.1.7 6 / 0
1.1.6 6 / 0
1.1.5 6 / 0
1.1.4 6 / 0
1.1.3 6 / 0
1.1.1 6 / 0

v1.1.10

1 finding
INFO No provenance attestation provenance

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

v1.1.9

1 finding
INFO No provenance attestation provenance

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

v1.1.8

1 finding
INFO No provenance attestation provenance

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

v1.1.7

1 finding
INFO No provenance attestation provenance

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

v1.1.5

1 finding
INFO No provenance attestation provenance

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

v1.1.4

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.

v1.1.3

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.

v1.1.1

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.