@form-create/utils
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 |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in a JSON/expression parser (makeFn) within a long-lived form-builder utility; stable pattern across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; empty description and link-dump README are cosmetic, not spam indicators. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 0 / 0 | |
| 2.7.17 | 0 / 1 | |
| 2.7.8 | 0 / 1 | |
| 2.7.0 | 0 / 1 | |
| 2.6.3 | 0 / 1 | |
| 2.6.2 | 0 / 1 | |
| 2.6.1 | 0 / 1 | |
| 2.6.0 | 0 / 0 | |
| 2.5.36 | 0 / 0 | |
| 2.5.35 | 0 / 0 | |
| 2.5.31 | 0 / 0 |
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.