@astrojs/language-server
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established scoped package with clear purpose and official repo; description omission is stable. | ai | |
| provenance | no-provenance | AI (provenance): Common for npm packages; not a blocker for established ecosystem tools. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Withastro org package with SLSA provenance; dormancy likely reflects release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:muggle-string | AI (dependencies): muggle-string is a standard utility in the Volar ecosystem; its use here is consistent with @volar/* dependencies throughout this package. | ai | |
| dependencies | unvetted-peer-dep:prettier-plugin-astro | AI (dependencies): prettier-plugin-astro is the official Astro prettier plugin and is an optional peer dep; stable false positive for this package. | ai | |
| provenance | slsa-provenance | AI (provenance): Official withastro package published via CI/CD with Sigstore SLSA attestation; this is a stable, positive signal for all versions of this package. | ai |
Versions (showing 74 of 74)
| Version | Deps | Published |
|---|---|---|
| 2.16.13 | 18 / 8 | |
| 2.16.12 | 18 / 8 | |
| 2.16.11 | 18 / 8 | |
| 2.16.10 | 18 / 8 | |
| 2.16.9 | 18 / 8 | |
| 2.16.8 | 18 / 8 | |
| 2.16.7 | 18 / 8 | |
| 2.16.6 | 18 / 8 | |
| 2.16.5 | 18 / 8 | |
| 2.16.4 | 18 / 8 | |
| 2.16.3 | 18 / 8 | |
| 2.16.2 | 18 / 8 | |
| 2.16.1 | 18 / 8 | |
| 2.16.0 | 18 / 8 | |
| 2.15.5 | 18 / 15 | |
| 2.15.4 | 18 / 15 | |
| 2.15.3 | 18 / 15 | |
| 2.15.0 | 18 / 15 | |
| 2.14.2 | 19 / 14 | |
| 2.14.1 | 19 / 14 | |
| 2.14.0 | 19 / 14 | |
| 2.13.4 | 17 / 14 | |
| 2.13.2 | 17 / 14 | |
| 2.13.1 | 17 / 14 | |
| 2.13.0 | 17 / 14 | |
| 2.12.8 | 17 / 14 | |
| 2.12.7 | 17 / 14 | |
| 2.12.1 | 17 / 14 | |
| 2.12.0 | 17 / 14 | |
| 2.11.1 | 17 / 14 | |
| 2.11.0 | 17 / 14 | |
| 2.10.0 | 16 / 14 | |
| 2.9.1 | 16 / 14 | |
| 2.9.0 | 16 / 14 | |
| 2.8.4 | 16 / 14 | |
| 2.8.3 | 16 / 14 | |
| 2.8.2 | 16 / 14 | |
| 2.8.1 | 16 / 14 | |
| 2.8.0 | 16 / 14 | |
| 2.7.7 | 16 / 14 | |
| 2.7.6 | 16 / 14 | |
| 2.7.5 | 16 / 14 | |
| 2.7.4 | 16 / 14 | |
| 2.7.3 | 16 / 13 | |
| 2.7.2 | 16 / 13 | |
| 2.7.1 | 16 / 13 | |
| 2.7.0 | 16 / 13 | |
| 2.6.3 | 18 / 12 | |
| 2.6.2 | 18 / 12 | |
| 2.6.1 | 18 / 12 | |
| 2.6.0 | 18 / 12 | |
| 2.5.5 | 18 / 12 | |
| 2.5.4 | 18 / 12 | |
| 2.5.3 | 18 / 12 | |
| 2.5.2 | 18 / 12 | |
| 2.5.1 | 18 / 12 | |
| 2.5.0 | 18 / 12 | |
| 2.4.1 | 18 / 12 | |
| 2.4.0 | 18 / 12 | |
| 2.3.4 | 18 / 12 | |
| 2.3.3 | 18 / 12 | |
| 2.3.2 | 18 / 12 | |
| 2.3.1 | 18 / 12 | |
| 2.3.0 | 18 / 12 | |
| 2.2.0 | 18 / 12 | |
| 2.1.4 | 18 / 12 | |
| 2.1.3 | 18 / 12 | |
| 2.1.2 | 18 / 12 | |
| 2.1.0 | 18 / 12 | |
| 2.0.17 | 18 / 13 | |
| 2.0.16 | 18 / 13 | |
| 2.0.15 | 17 / 13 | |
| 2.0.14 | 17 / 13 | |
| 2.0.0 | 17 / 13 |
v2.16.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.15.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.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.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
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.0.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.