@websolutespa/payload-plugin-seo
SEO 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): Established, purpose-relevant React input library; no exec/exfil behavior. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (amaca, army75, ldeblasio) appear to be org members; publisher actarian is a known prior maintainer. | ai | |
| phantom-deps | phantom-dep:ts-deepmerge | AI (phantom-deps): ts-deepmerge is a declared runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 2 / 26 | |
| 3.0.0 | 2 / 26 | |
| 2.0.0 | 2 / 15 | |
| 0.1.4 | 2 / 15 | |
| 0.1.3 | 2 / 15 | |
| 0.1.2 | 2 / 15 | |
| 0.1.1 | 2 / 15 | |
| 0.1.0 | 2 / 15 | |
| 0.0.3 | 2 / 15 | |
| 0.0.2 | 2 / 15 | |
| 0.0.1 | 1 / 15 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (m.fort) than the most recent previously approved version (actarian) on 2025-03-05, but m.fort is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (actarian) than the most recent previously approved version (m.fort) on 2024-09-20, but actarian is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (actarian) than the most recent previously approved version (m.fort) on 2024-09-20, but actarian is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (actarian) than the most recent previously approved version (m.fort) on 2024-09-18, but actarian is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.