@sveltejs/adapter-node
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Svelte org migrated to GitHub Actions CI publishing; SLSA attestation confirms legitimate pipeline origin. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 5.5.7 | 5 / 7 | |
| 5.5.6 | 5 / 7 | |
| 5.5.5 | 5 / 7 | |
| 5.5.4 | 4 / 8 | |
| 5.5.3 | 4 / 8 | |
| 5.5.2 | 4 / 8 | |
| 5.5.1 | 4 / 8 | |
| 5.4.0 | 4 / 8 | |
| 5.3.3 | 4 / 8 | |
| 5.3.2 | 4 / 8 | |
| 5.3.1 | 4 / 8 | |
| 5.3.0 | 4 / 8 | |
| 5.2.16 | 4 / 8 | |
| 5.2.15 | 4 / 8 | |
| 5.2.14 | 4 / 8 | |
| 5.2.13 | 4 / 8 | |
| 5.2.12 | 4 / 8 | |
| 5.2.11 | 4 / 8 | |
| 5.2.10 | 4 / 8 | |
| 5.2.9 | 4 / 8 | |
| 5.2.8 | 4 / 8 | |
| 5.2.7 | 4 / 8 | |
| 5.2.6 | 4 / 8 | |
| 5.2.5 | 4 / 8 | |
| 5.2.4 | 4 / 8 | |
| 5.2.3 | 4 / 8 | |
| 5.2.2 | 4 / 8 | |
| 5.2.1 | 4 / 8 | |
| 5.2.0 | 4 / 8 | |
| 5.1.1 | 4 / 8 | |
| 5.1.0 | 4 / 8 | |
| 5.0.2 | 4 / 9 | |
| 5.0.1 | 4 / 9 | |
| 5.0.0 | 4 / 9 |
v5.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.