← Home

@generaltranslation/supported-locales

npm Repository Homepage

List of supported locales for General Translation

79
Versions
FSL-1.1-ALv2
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

archiemckenziebgubernest-general-translationbrian_lou

Keywords

internal

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Established package in the generaltranslation org; provenance gap reflects CI change, not malicious intent. ai
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions with SLSA attestation; reflects CI/CD automation, stable for this package. ai

Versions (showing 79 of 79)

Version Deps Published
2.1.11 1 / 2
2.1.10 1 / 2
2.1.9 1 / 2
2.1.8 1 / 2
2.1.7 1 / 2
2.1.5 1 / 2
2.1.4 1 / 2
2.1.3 1 / 2
2.1.2 1 / 2
2.1.1 1 / 2
2.1.0 1 / 2
2.0.73 1 / 2
2.0.72 1 / 2
2.0.71 1 / 2
2.0.70 1 / 2
2.0.69 1 / 2
2.0.68 1 / 2
2.0.67 1 / 2
2.0.66 1 / 2
2.0.65 1 / 2
2.0.64 1 / 7
2.0.63 1 / 7
2.0.62 1 / 7
2.0.61 1 / 7
2.0.60 1 / 7
2.0.59 1 / 7
2.0.58 1 / 7
2.0.57 1 / 7
2.0.56 1 / 7
2.0.55 1 / 7
2.0.54 1 / 7
2.0.53 1 / 7
2.0.52 1 / 7
2.0.51 1 / 7
2.0.50 1 / 7
2.0.49 1 / 7
2.0.48 1 / 7
2.0.47 1 / 7
2.0.46 1 / 7
2.0.45 1 / 7
2.0.44 1 / 7
2.0.43 1 / 7
2.0.42 1 / 7
2.0.41 1 / 7
2.0.40 1 / 7
2.0.39 1 / 7
2.0.38 1 / 7
2.0.37 1 / 7
2.0.36 1 / 7
2.0.35 1 / 7
2.0.34 1 / 7
2.0.33 1 / 7
2.0.32 1 / 7
2.0.31 1 / 7
2.0.30 1 / 7
2.0.29 1 / 7
2.0.28 1 / 7
2.0.27 1 / 7
2.0.26 1 / 7
2.0.25 1 / 7
2.0.24 1 / 7
2.0.23 1 / 7
2.0.22 1 / 7
2.0.21 1 / 7
2.0.16 1 / 7
2.0.14 1 / 7
2.0.13 1 / 7
2.0.12 1 / 7
2.0.11 1 / 7
2.0.10 1 / 7
2.0.9 1 / 7
2.0.8 1 / 7
2.0.7 1 / 7
2.0.6 1 / 7
2.0.4 1 / 7
2.0.3 1 / 7
2.0.2 1 / 7
2.0.1 1 / 7
2.0.0 1 / 7

v2.1.11

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.10

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.8

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.7

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.5

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.7

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.

v2.0.6

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.

v2.0.4

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.

v2.0.3

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.

v2.0.2

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.

v2.0.1

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.

v2.0.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.