← Home

@djangocfg/i18n

npm Repository Homepage

Lightweight i18n library for @djangocfg packages with built-in translations for English, Russian, and Korean

100
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

markolofsen

Keywords

i18ninternationalizationlocalizationtranslationsreactnextjstypescript

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Consistent across all @djangocfg packages; publisher has strong approval track record. ai

Versions (showing 100 of 246)

Version Deps Published
2.1.310 2 / 6
2.1.309 2 / 6
2.1.308 2 / 6
2.1.307 2 / 6
2.1.304 2 / 6
2.1.303 2 / 6
2.1.302 2 / 6
2.1.301 2 / 6
2.1.300 2 / 6
2.1.299 2 / 6
2.1.298 2 / 6
2.1.297 2 / 6
2.1.294 2 / 6
2.1.293 2 / 6
2.1.292 2 / 6
2.1.291 2 / 6
2.1.290 2 / 6
2.1.289 2 / 6
2.1.287 2 / 6
2.1.286 2 / 6
2.1.285 2 / 6
2.1.284 2 / 6
2.1.283 2 / 6
2.1.282 2 / 6
2.1.281 2 / 6
2.1.280 2 / 6
2.1.279 2 / 6
2.1.277 2 / 6
2.1.276 2 / 6
2.1.275 2 / 6
2.1.274 2 / 6
2.1.272 2 / 6
2.1.271 2 / 6
2.1.270 2 / 6
2.1.268 2 / 6
2.1.267 2 / 6
2.1.266 2 / 6
2.1.264 2 / 6
2.1.263 2 / 6
2.1.262 2 / 6
2.1.261 2 / 6
2.1.260 2 / 6
2.1.259 2 / 6
2.1.257 2 / 6
2.1.256 2 / 6
2.1.255 2 / 6
2.1.254 2 / 6
2.1.252 2 / 6
2.1.251 2 / 6
2.1.249 2 / 6
2.1.248 2 / 6
2.1.247 2 / 6
2.1.246 2 / 6
2.1.243 2 / 6
2.1.242 2 / 6
2.1.241 2 / 6
2.1.240 2 / 6
2.1.239 2 / 6
2.1.238 2 / 6
2.1.237 2 / 6
2.1.236 2 / 6
2.1.235 2 / 6
2.1.234 2 / 6
2.1.233 2 / 6
2.1.232 2 / 6
2.1.231 2 / 6
2.1.230 2 / 6
2.1.229 2 / 6
2.1.228 2 / 6
2.1.227 2 / 6
2.1.226 2 / 6
2.1.225 2 / 6
2.1.224 2 / 6
2.1.223 2 / 6
2.1.222 2 / 6
2.1.221 2 / 6
2.1.219 2 / 6
2.1.218 2 / 6
2.1.215 4 / 6
2.1.212 4 / 6
2.1.208 4 / 6
2.1.206 4 / 6
2.1.203 4 / 6
2.1.198 4 / 6
2.1.194 4 / 6
2.1.192 4 / 6
2.1.189 4 / 6
2.1.186 4 / 6
2.1.183 4 / 6
2.1.182 4 / 6
2.1.181 4 / 6
2.1.180 4 / 6
2.1.178 4 / 6
2.1.177 4 / 6
2.1.172 4 / 6
2.1.170 4 / 6
2.1.165 4 / 6
2.1.164 4 / 6
2.1.163 0 / 5
2.1.162 0 / 4
Showing 100 of 246 Next page →

v2.1.242

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.

v2.1.241

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.

v2.1.240

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.

v2.1.239

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.

v2.1.238

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.

v2.1.237

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.

v2.1.236

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.

v2.1.235

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.

v2.1.234

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.

v2.1.233

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.

v2.1.232

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.

v2.1.231

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.

v2.1.230

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.

v2.1.229

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.

v2.1.228

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.

v2.1.227

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.

v2.1.226

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.

v2.1.225

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.

v2.1.224

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.

v2.1.223

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.

v2.1.222

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.

v2.1.221

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.

v2.1.219

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.

v2.1.218

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.

v2.1.215

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.

v2.1.212

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.

v2.1.208

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.

v2.1.206

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.

v2.1.203

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.

v2.1.198

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.

v2.1.194

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.

v2.1.192

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.

v2.1.189

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.

v2.1.186

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.

v2.1.183

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.

v2.1.182

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.

v2.1.177

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.

v2.1.172

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.

v2.1.170

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.

v2.1.165

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.

v2.1.164

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.

v2.1.163

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.

v2.1.162

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.