← Home

@mock-locale/az

Azerbaijani locale data for ts-mocker

7
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

chrisbreuer

Keywords

ts-mockerts-fakerts-mockerlocaleazazerbaijaniazerbaijanfake-datatest-data

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped locale package; Levenshtein match to 'pg' is coincidental, not a typosquat. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped locale package; Levenshtein match to 'qs' is coincidental, not a typosquat. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped locale package; Levenshtein match to 'ajv' is coincidental, not a typosquat. ai

Versions (showing 7 of 7)

Version Deps Published
0.1.8 0 / 4
0.1.7 0 / 4
0.1.6 0 / 4
0.1.5 0 / 4
0.1.4 0 / 4
0.1.3 0 / 4
0.1.2 0 / 4

v0.1.8

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.

v0.1.7

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.

v0.1.6

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.

v0.1.5

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.

v0.1.4

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.

v0.1.3

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.

v0.1.2

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.