@cluesurf/form
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Declared dep used transitively or in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@termsurf/have | AI (phantom-deps): Referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@termsurf/kink | AI (phantom-deps): Referenced in config; stable false positive. | ai | |
| phantom-deps | phantom-dep:@cluesurf/love-code | AI (phantom-deps): Same-org scope config dep; stable false positive. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @cluesurf/form is unrelated to cors; Levenshtein match is coincidental. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.9.10 | 5 / 9 | |
| 0.9.8 | 5 / 9 | |
| 0.9.6 | 5 / 9 | |
| 0.9.4 | 5 / 9 | |
| 0.9.2 | 4 / 9 | |
| 0.9.0 | 4 / 9 | |
| 0.8.34 | 4 / 8 | |
| 0.8.28 | 4 / 8 | |
| 0.8.20 | 4 / 8 | |
| 0.8.6 | 4 / 8 | |
| 0.8.4 | 4 / 8 | |
| 0.8.2 | 4 / 8 | |
| 0.8.0 | 4 / 9 | |
| 0.7.4 | 4 / 9 | |
| 0.7.2 | 4 / 9 | |
| 0.7.0 | 4 / 9 | |
| 0.6.28 | 4 / 9 | |
| 0.6.26 | 4 / 9 | |
| 0.6.24 | 4 / 9 | |
| 0.6.22 | 4 / 9 | |
| 0.6.20 | 4 / 9 | |
| 0.6.10 | 4 / 9 | |
| 0.6.8 | 4 / 9 | |
| 0.6.4 | 4 / 9 | |
| 0.6.2 | 4 / 9 | |
| 0.6.0 | 6 / 8 |
v0.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.