@swan-io/use-form
2
Versions
—
License
No
Install Scripts
Verified
Provenance
Supply chain provenance
Status for the latest visible version.
SLSA provenance attestation
npm registry signatures
No source commit
Maintainers
swan-io
Keywords
formhookreacttypescriptuxvalidation
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA provenance attestation; consistent with CI/CD automation for swan-io org. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a major version bump with SLSA provenance is consistent with intentional release, not takeover. | ai | |
| dependencies | unvetted-dep:@bloodyowl/boxed | AI (dependencies): Replaces @swan-io/boxed; appears to be a legitimate upstream rename within the same author ecosystem. | ai |
v4.0.0
2 findings
HIGH
Publisher changed: swan-io → GitHub Actions (on 2026-05-18)
provenance
This version was published by a different npm account than previous versions on 2026-05-18. This could indicate a legitimate maintainer transition or an account compromise.
INFO
Has SLSA provenance attestation
provenance
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.0
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.