@prezly/theme-kit-intl
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Prezly org package; lack of provenance is consistent across all versions and not a risk signal here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 10.9.0 | 1 / 1 | |
| 10.8.0 | 1 / 1 | |
| 10.6.2 | 1 / 1 | |
| 10.6.1 | 1 / 1 | |
| 10.3.0 | 1 / 1 | |
| 10.2.2 | 1 / 1 | |
| 10.2.1 | 1 / 1 | |
| 10.2.0 | 1 / 1 | |
| 10.1.2 | 1 / 1 | |
| 10.1.1 | 1 / 1 | |
| 10.1.0 | 1 / 1 | |
| 7.8.0 | 1 / 7 |
v10.9.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jessewynants) than the most recent previously approved version (francis-prezly) on 2026-07-22, but jessewynants is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kudlik) than the most recent previously approved version (e1npm) on 2025-04-22, but kudlik is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (e1npm) than the most recent previously approved version (yuriyyakym) on 2025-03-12, but e1npm is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (yuriyyakym) than the most recent previously approved version (francis-prezly) on 2025-02-26, but yuriyyakym is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.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.
v10.1.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.