@plone/registry
Add-on and configuration registry for Plone and for JavaScript and TypeScript-based apps.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): deepmerge is a well-established, widely-used utility with no malicious history; low risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Plone Foundation package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 7 / 13 | |
| 3.0.0 | 7 / 13 | |
| 2.7.3 | 6 / 13 | |
| 2.7.2 | 6 / 13 | |
| 2.7.1 | 6 / 14 | |
| 2.7.0 | 6 / 14 | |
| 2.6.0 | 6 / 14 | |
| 2.5.4 | 6 / 14 | |
| 2.5.3 | 6 / 14 | |
| 2.5.2 | 6 / 14 | |
| 2.5.1 | 6 / 14 | |
| 2.5.0 | 6 / 14 | |
| 2.4.1 | 6 / 14 | |
| 2.4.0 | 6 / 16 | |
| 2.3.0 | 6 / 16 | |
| 2.2.0 | 6 / 16 | |
| 2.1.2 | 6 / 16 | |
| 2.1.1 | 6 / 16 |
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.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.