@plone/scripts
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Config-file-only reference; stable false positive for this tooling package. | ai | |
| phantom-deps | phantom-dep:git-url-parse | AI (phantom-deps): Config-file-only reference; stable false positive for this tooling package. | ai | |
| phantom-deps | phantom-dep:mrs-developer | AI (phantom-deps): Config-file-only reference; stable false positive for this tooling package. | ai | |
| phantom-deps | phantom-dep:@plone/babel-preset-razzle | AI (phantom-deps): Same-org scoped dep used in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-preset-razzle | AI (phantom-deps): Referenced in config files as a babel preset, not directly imported — stable false positive for this build tooling package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-react-intl | AI (phantom-deps): Referenced in config files as a babel plugin, not directly imported — stable false positive for this build tooling package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used in the addon registry loader to resolve project-specific addon paths at build time — expected pattern for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.0.1 | 15 / 1 | |
| 4.0.0 | 15 / 1 | |
| 3.10.6 | 15 / 1 | |
| 3.10.5 | 15 / 1 | |
| 3.10.4 | 15 / 1 | |
| 3.10.3 | 15 / 1 | |
| 3.10.2 | 15 / 1 | |
| 3.10.1 | 15 / 1 | |
| 3.10.0 | 15 / 1 |
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.