@electerm/electerm-locales
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:ssh-key-access | AI (semgrep): Fires on locale/translation string keys referencing SSH terminology, not actual credential access code. Stable false positive for this locales package. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 2.2.18 | 0 / 9 | |
| 2.2.17 | 0 / 9 | |
| 2.2.16 | 0 / 9 | |
| 2.2.14 | 0 / 9 | |
| 2.2.12 | 0 / 9 | |
| 2.2.10 | 0 / 9 | |
| 2.2.9 | 0 / 10 | |
| 2.2.6 | 0 / 10 | |
| 2.2.5 | 0 / 10 | |
| 2.2.4 | 0 / 10 | |
| 2.2.3 | 0 / 10 | |
| 2.2.2 | 0 / 10 | |
| 2.2.1 | 0 / 10 | |
| 2.2.0 | 0 / 10 | |
| 2.1.66 | 0 / 10 | |
| 2.1.65 | 0 / 10 | |
| 2.1.64 | 0 / 10 | |
| 2.1.63 | 0 / 10 | |
| 2.1.61 | 0 / 10 | |
| 2.1.60 | 0 / 10 | |
| 2.1.59 | 0 / 10 | |
| 2.1.58 | 0 / 10 | |
| 2.1.57 | 0 / 10 | |
| 2.1.56 | 0 / 10 | |
| 2.1.55 | 0 / 10 | |
| 2.1.53 | 0 / 10 | |
| 2.1.51 | 0 / 10 | |
| 2.1.49 | 0 / 10 | |
| 2.1.48 | 0 / 10 | |
| 2.1.47 | 0 / 10 | |
| 2.1.46 | 0 / 10 | |
| 2.1.45 | 0 / 10 | |
| 2.1.44 | 0 / 10 | |
| 2.0.37 | 0 / 10 | |
| 2.0.36 | 0 / 10 | |
| 2.0.35 | 0 / 10 | |
| 2.0.34 | 0 / 10 | |
| 2.0.33 | 0 / 10 | |
| 2.0.29 | 0 / 10 | |
| 2.0.28 | 0 / 10 | |
| 2.0.27 | 0 / 11 | |
| 2.0.26 | 0 / 11 | |
| 2.0.25 | 0 / 11 | |
| 2.0.24 | 0 / 11 | |
| 2.0.23 | 0 / 11 | |
| 2.0.21 | 0 / 11 | |
| 2.0.20 | 0 / 11 | |
| 2.0.19 | 0 / 11 | |
| 2.0.15 | 0 / 11 | |
| 2.0.11 | 0 / 11 | |
| 2.0.10 | 0 / 11 | |
| 2.0.9 | 0 / 11 | |
| 2.0.3 | 0 / 11 | |
| 2.0.1 | 0 / 11 | |
| 2.0.0 | 0 / 11 |
v2.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.