@unchainedshop/core-countries
Country management module for the Unchained Engine
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established monorepo package; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 4.8.13 | 2 / 2 | |
| 4.8.12 | 2 / 2 | |
| 4.8.11 | 2 / 2 | |
| 4.8.10 | 2 / 2 | |
| 4.8.9 | 2 / 2 | |
| 4.8.4 | 2 / 2 | |
| 4.8.3 | 2 / 2 | |
| 4.8.2 | 2 / 2 | |
| 4.8.1 | 2 / 2 | |
| 4.8.0 | 2 / 2 | |
| 4.7.2 | 2 / 2 | |
| 4.6.2 | 2 / 2 | |
| 4.6.1 | 2 / 2 | |
| 4.6.0 | 2 / 2 | |
| 4.5.0 | 2 / 2 | |
| 4.4.0 | 2 / 2 | |
| 4.3.4 | 2 / 3 | |
| 4.3.3 | 2 / 3 | |
| 4.3.2 | 2 / 3 | |
| 4.3.1 | 2 / 3 | |
| 4.3.0 | 2 / 3 | |
| 4.2.0 | 2 / 3 | |
| 4.1.3 | 2 / 3 | |
| 4.1.2 | 2 / 3 | |
| 4.1.1 | 2 / 3 | |
| 4.1.0 | 2 / 3 | |
| 4.0.2 | 2 / 3 | |
| 4.0.1 | 2 / 3 | |
| 4.0.0 | 2 / 3 |
v4.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.