svelte-language-server
A language server for Svelte
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sveltejs/load-config | AI (dependencies): First-party @sveltejs/ scoped package from the same org as svelte-language-server; low risk. | ai | |
| provenance | publisher-changed | AI (provenance): Migration from svelte-language-tools-deploy to GitHub Actions CI; SLSA attestation confirms official sveltejs org repo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by CI pipeline migration; SLSA provenance confirms legitimate publish from official repo. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.18.3 | 19 / 11 | |
| 0.18.2 | 19 / 11 | |
| 0.18.1 | 18 / 11 | |
| 0.18.0 | 18 / 11 | |
| 0.17.31 | 19 / 10 | |
| 0.17.30 | 19 / 10 | |
| 0.17.29 | 19 / 10 | |
| 0.17.28 | 19 / 10 | |
| 0.17.27 | 19 / 10 | |
| 0.17.26 | 19 / 10 | |
| 0.17.25 | 19 / 10 | |
| 0.17.24 | 19 / 10 | |
| 0.17.23 | 19 / 10 | |
| 0.17.22 | 19 / 10 | |
| 0.17.21 | 19 / 10 | |
| 0.17.20 | 19 / 10 | |
| 0.17.19 | 19 / 10 | |
| 0.17.18 | 19 / 10 | |
| 0.17.17 | 19 / 10 | |
| 0.17.16 | 19 / 10 | |
| 0.17.15 | 19 / 10 | |
| 0.17.14 | 19 / 10 | |
| 0.17.13 | 19 / 10 | |
| 0.17.12 | 19 / 10 | |
| 0.17.11 | 19 / 10 | |
| 0.17.10 | 19 / 10 | |
| 0.17.9 | 19 / 10 | |
| 0.17.8 | 19 / 10 | |
| 0.17.7 | 19 / 10 | |
| 0.17.6 | 19 / 10 | |
| 0.17.5 | 19 / 10 | |
| 0.17.4 | 19 / 10 | |
| 0.17.3 | 18 / 11 | |
| 0.17.2 | 18 / 9 | |
| 0.17.1 | 18 / 9 | |
| 0.17.0 | 18 / 9 | |
| 0.16.14 | 19 / 10 | |
| 0.16.13 | 19 / 10 | |
| 0.16.12 | 19 / 10 | |
| 0.16.11 | 19 / 10 | |
| 0.16.10 | 19 / 10 |
v0.17.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.