@payloadcms/plugin-form-builder
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): First-party @payloadcms/* dep pinned to matching version; normal monorepo pattern. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth from bundling translations/locale files, not injected payload. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Consistent with adding translation language files across monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): PayloadCMS monorepo packages consistently lack Sigstore attestation; stable false positive for this publisher. | ai |
Versions (showing 15 of 115)
| Version | Deps | Published |
|---|---|---|
| 3.9.0 | 2 / 7 | |
| 3.8.0 | 2 / 7 | |
| 3.7.0 | 2 / 7 | |
| 3.6.0 | 2 / 7 | |
| 3.5.0 | 2 / 7 | |
| 3.4.0 | 2 / 7 | |
| 3.3.0 | 2 / 7 | |
| 3.2.2 | 2 / 7 | |
| 3.2.1 | 2 / 7 | |
| 3.2.0 | 2 / 7 | |
| 3.1.1 | 2 / 7 | |
| 3.1.0 | 2 / 7 | |
| 3.0.2 | 2 / 7 | |
| 3.0.1 | 2 / 7 | |
| 3.0.0 | 2 / 7 |
v3.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.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.
v3.2.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.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.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.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.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.
v3.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.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.