@websolutespa/payload-plugin-seed
Seed data plugin for PayloadCms
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:react-autocomplete-input | AI (dependencies): Phantom-dep findings confirm it's not directly imported; used as a UI peer dep in a CMS plugin context, low risk. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers appear to be within the same @websolutespa org; consistent publisher history with no rejections. | ai | |
| 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 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 2 / 25 | |
| 3.0.1 | 2 / 25 | |
| 3.0.0 | 2 / 25 | |
| 2.0.0 | 2 / 15 | |
| 0.0.10 | 2 / 15 | |
| 0.0.9 | 2 / 15 | |
| 0.0.8 | 2 / 15 | |
| 0.0.7 | 2 / 15 | |
| 0.0.6 | 2 / 15 | |
| 0.0.5 | 2 / 15 | |
| 0.0.4 | 2 / 15 | |
| 0.0.3 | 2 / 15 | |
| 0.0.2 | 2 / 15 | |
| 0.0.1 | 2 / 15 |
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.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.
v0.0.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.