@websolutespa/payload-plugin-seed
Seed data plugin for PayloadCms
4
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
websolute-adminactariancbrualdifedericodilucagiacomo_grassettim.fortldeblasio
Keywords
payloadseed
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established org package; lack of Sigstore attestation is a process gap, not a security signal for this package. | ai | |
| phantom-deps | phantom-dep:ts-deepmerge | AI (phantom-deps): Declared runtime dep used indirectly via compiled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-autocomplete-input | AI (phantom-deps): UI component dep likely referenced in compiled/bundled output; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.0.10 | 2 / 15 | |
| 0.0.9 | 2 / 15 | |
| 0.0.8 | 2 / 15 | |
| 0.0.6 | 2 / 15 |
v0.0.9
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.