@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 — 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 |
|---|---|---|---|---|
| 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 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 10.6.1 | 8 / 1 | |
| 10.6.0 | 8 / 1 | |
| 10.5.4 | 8 / 1 | |
| 10.5.3 | 8 / 1 | |
| 10.5.0 | 8 / 1 | |
| 10.3.1 | 8 / 1 | |
| 7.9.0 | 5 / 1 | |
| 7.8.0 | 5 / 1 |
v10.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.5.3
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.5.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.
v10.3.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.
v7.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.