@puckeditor/plugin-ai
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:qler | AI (dependencies): qler is a small utility dep in a legitimate puck monorepo plugin; no malicious indicators found. | ai | |
| provenance | no-provenance | AI (provenance): Established puckeditor org package; lack of provenance is common and not a risk signal here. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo plugin package; missing description is a cosmetic gap, not a malware indicator. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 7 / 16 | |
| 0.6.0 | 7 / 16 | |
| 0.4.0 | 7 / 16 | |
| 0.3.1 | 6 / 16 | |
| 0.2.0 | 6 / 16 | |
| 0.1.0 | 5 / 17 | |
| 0.0.1 | 9 / 12 |
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage 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.