← Home

@sourceregistry/sveltekit-enhance

Composable enhance and form utilities for SvelteKit actions, loads, methods, and hooks.

15
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

alexander2000

Keywords

sveltekitsveltekitmiddlewareguardsactionshookshookloadformvalidationfeature-flagsobservability

Versions (showing 15 of 15)

Version Deps Published
1.7.1 0 / 18
1.7.0 0 / 18
1.6.0 0 / 18
1.5.1 0 / 18
1.5.0 0 / 18
1.3.3 0 / 18
1.3.2 0 / 18
1.3.1 0 / 18
1.3.0 0 / 18
1.2.0 0 / 18
1.1.2 0 / 18
1.1.1 0 / 18
1.1.0 0 / 18
1.0.1 0 / 18
1.0.0 0 / 18

v1.7.1

1 finding
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.

v1.7.0

1 finding
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.

v1.6.0

1 finding
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.

v1.5.1

1 finding
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.

v1.5.0

2 findings
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.

INFO Publisher changed: alexander2000 → GitHub Actions (on 2026-07-12, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (alexander2000) on 2026-07-12, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.