← Home

@better-intl/next

npm

Next.js App Router integration for better-intl

22
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

tsunode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:nuxt AI (typosquat): Scoped i18n package for Next.js; name similarity to nuxt is incidental, not a squatting attempt. ai
typosquat typosquat.levenshtein:jest AI (typosquat): 2-edit distance to jest is noise; package is clearly an i18n integration library. ai
typosquat typosquat.levenshtein:knex AI (typosquat): 2-edit distance to knex is noise; unrelated domain. ai

Versions (showing 22 of 22)

Version Deps Published
0.11.1 2 / 0
0.11.0 2 / 0
0.10.0 2 / 0
0.9.0 2 / 0
0.8.0 2 / 0
0.7.0 2 / 0
0.6.4 2 / 0
0.6.3 2 / 0
0.6.2 2 / 0
0.6.1 2 / 0
0.6.0 2 / 0
0.4.0 2 / 0
0.3.3 2 / 0
0.3.2 2 / 0
0.3.1 2 / 0
0.3.0 2 / 0
0.2.1 2 / 0
0.2.0 2 / 0
0.1.3 2 / 0
0.1.2 2 / 0
0.1.1 2 / 0
0.1.0 2 / 0

v0.11.1

1 finding
LOW No provenance attestation provenance

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

v0.11.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'nuxt' typosquat

Package name '@better-intl/next' is 1 edit(s) away from popular package 'nuxt'.

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.

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.3

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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