sveltekit-superforms
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@gcornut/valibot-json-schema | AI (dependencies): Optional dep for valibot JSON schema conversion; consistent with package's multi-adapter design, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:zod-v3-to-json-schema | AI (dependencies): Optional validation adapter for zod v3 JSON schema conversion; consistent with package's multi-schema architecture. | ai | |
| dependencies | unvetted-dep:@typeschema/class-validator | AI (dependencies): Optional class-validator adapter; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:class-validator | AI (phantom-deps): class-validator is an explicitly declared optional peer dependency; not directly imported by design. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 230 versions; lack of provenance is consistent across all prior releases. | ai | |
| dependencies | unvetted-dep:memoize-weak | AI (dependencies): memoize-weak is a small, stable utility; no known issues and appropriate for this package's use case. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.30.1 | 3 / 36 | |
| 2.30.0 | 3 / 36 | |
| 2.29.1 | 18 / 36 | |
| 2.29.0 | 17 / 37 | |
| 2.28.1 | 18 / 36 | |
| 2.28.0 | 18 / 36 | |
| 2.27.4 | 18 / 36 |
v2.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.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.
v2.27.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.