← Home

@cluesurf/form

npm
42
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

lancejpollard

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Renaming from @termsurf to @cluesurf namespace by same maintainer, not a foreign dependency injection. ai
dependencies unvetted-dep:@cluesurf/form-code AI (dependencies): Same-author sibling package, part of author's own monorepo ecosystem. ai
phantom-deps phantom-dep:@termsurf/have 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
phantom-deps phantom-dep:@termsurf/kink AI (phantom-deps): Referenced in config; stable false positive. ai
phantom-deps phantom-dep:dayjs AI (phantom-deps): Declared dep used transitively or in config; stable false positive for this package. ai
typosquat typosquat.levenshtein:cors AI (typosquat): Scoped package @cluesurf/form is unrelated to cors; Levenshtein match is coincidental. ai

Versions (showing 42 of 42)

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
0.5.8 6 / 8
0.5.6 6 / 8
0.5.4 6 / 8
0.5.2 6 / 8
0.5.0 6 / 8
0.4.6 6 / 8
0.4.4 6 / 8
0.4.2 6 / 8
0.4.0 6 / 8
0.3.0 5 / 25
0.2.0 5 / 25
0.1.10 5 / 25
0.1.8 5 / 25
0.1.6 5 / 25
0.1.4 5 / 25
0.1.2 5 / 25

v0.5.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.10

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.