← Home

@uxf/localize

npm
25
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

uxf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Consistent across all versions of this package; not a security risk on its own. ai
dependencies unvetted-dep:currency.js AI (dependencies): currency.js is a well-known, stable currency formatting library; stable dependency for this package. ai

Versions (showing 25 of 25)

Version Deps Published
11.122.4 1 / 7
11.122.2 1 / 7
11.120.0 1 / 7
11.119.0 1 / 7
11.114.0 1 / 6
11.111.2 1 / 6
11.110.0 1 / 6
11.108.0 1 / 6
11.107.0 2 / 5
11.92.1 2 / 2
11.90.0 2 / 2
11.88.2 2 / 2
11.88.0 2 / 2
11.86.0 2 / 2
11.80.4 2 / 2
11.79.0 2 / 2
11.78.0 2 / 2
11.63.0 2 / 2
11.62.2 2 / 2
11.47.0 2 / 2
11.46.0 2 / 2
11.45.0 2 / 2
11.32.0 2 / 2
11.29.0 2 / 2
11.22.0 2 / 2

v11.122.4

1 finding
INFO No provenance attestation provenance

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

v11.122.2

1 finding
INFO No provenance attestation provenance

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

v11.47.0

1 finding
INFO No provenance attestation provenance

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

v11.46.0

1 finding
INFO No provenance attestation provenance

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

v11.45.0

1 finding
INFO No provenance attestation provenance

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

v11.32.0

1 finding
INFO No provenance attestation provenance

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

v11.29.0

1 finding
INFO No provenance attestation provenance

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

v11.22.0

1 finding
INFO No provenance attestation provenance

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