@prezly/theme-kit-nextjs
Data layer and utility library for developing Prezly themes with NextJS
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@prezly/theme-kit-intl | AI (dependencies): First-party Prezly monorepo sibling, versioned in lockstep. | ai | |
| dependencies | unvetted-dep:@prezly/theme-kit-react | AI (dependencies): First-party Prezly monorepo sibling, versioned in lockstep. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainer is a known Prezly team member per provenance record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal team rotation for long-lived org package, not a takeover pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Large version restructure from v10.x to v7.x branch; dormancy explained by parallel development track. | ai | |
| dependencies | unvetted-dep:@technically/omit-undefined | AI (dependencies): Small utility from @technically namespace; same org already used via @technically/is-not-undefined in this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Prezly org package; no provenance is consistent across all 390 versions. | ai | |
| phantom-deps | phantom-dep:url-pattern | AI (phantom-deps): url-pattern is a declared runtime dep in package.json; phantom-dep false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 10.9.0 | 8 / 1 | |
| 10.8.0 | 8 / 1 | |
| 10.7.0 | 8 / 1 | |
| 10.6.2 | 8 / 1 | |
| 10.6.1 | 8 / 1 | |
| 10.6.0 | 8 / 1 | |
| 10.5.4 | 8 / 1 | |
| 10.5.3 | 8 / 1 | |
| 10.5.2 | 8 / 1 | |
| 10.5.1 | 8 / 1 | |
| 10.5.0 | 8 / 1 | |
| 10.4.0 | 8 / 1 | |
| 10.3.1 | 8 / 1 | |
| 10.3.0 | 8 / 1 | |
| 10.2.3 | 8 / 1 | |
| 10.2.2 | 8 / 1 | |
| 10.2.1 | 8 / 1 | |
| 10.2.0 | 8 / 1 | |
| 10.1.2 | 8 / 1 | |
| 10.1.1 | 8 / 1 | |
| 10.1.0 | 8 / 1 | |
| 7.9.0 | 5 / 1 | |
| 7.8.0 | 5 / 1 |
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.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.5.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-09-26, 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.5.1
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 (e1npm) on 2025-09-24, 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.4.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 (e1npm) than the most recent previously approved version (kudlik) on 2025-09-05, 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.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.3
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 (e1npm) on 2025-03-14, 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.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.