@redocly/openapi-language-server
Redocly OpenAPI language server
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:vscode-uri | AI (phantom-deps): Bundled language-server; deps consumed at build time, not via direct ESM imports. | ai | |
| phantom-deps | phantom-dep:@redocly/config | AI (phantom-deps): Same-org dep used in build/bundle pipeline, not a direct import. | ai | |
| phantom-deps | phantom-dep:vscode-languageserver | AI (phantom-deps): Bundled language-server; deps consumed at build time. | ai | |
| phantom-deps | phantom-dep:vscode-languageserver-textdocument | AI (phantom-deps): Bundled language-server; deps consumed at build time. | ai | |
| phantom-deps | phantom-dep:@redocly/yaml-language-server-parser | AI (phantom-deps): Same-org dep used in build/bundle pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped Redocly org package with 110 versions; sparse metadata is a packaging style choice, not spam. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 0.9.2 | 5 / 7 | |
| 0.9.1 | 5 / 7 | |
| 0.9.0 | 5 / 7 | |
| 0.8.13 | 5 / 7 | |
| 0.8.12 | 5 / 7 | |
| 0.8.11 | 5 / 7 | |
| 0.8.10 | 5 / 7 | |
| 0.8.9 | 5 / 7 | |
| 0.8.4 | 5 / 7 | |
| 0.8.2 | 5 / 7 | |
| 0.6.19 | 5 / 7 | |
| 0.6.18 | 5 / 7 | |
| 0.6.17 | 5 / 7 | |
| 0.6.16 | 5 / 7 | |
| 0.6.15 | 5 / 7 | |
| 0.6.14 | 5 / 7 | |
| 0.6.13 | 5 / 7 | |
| 0.6.12 | 5 / 7 | |
| 0.6.11 | 5 / 7 | |
| 0.6.10 | 5 / 7 | |
| 0.6.9 | 5 / 7 | |
| 0.6.8 | 5 / 7 | |
| 0.6.7 | 5 / 7 | |
| 0.6.6 | 5 / 7 | |
| 0.6.5 | 5 / 7 | |
| 0.6.4 | 5 / 7 | |
| 0.6.3 | 5 / 7 | |
| 0.6.2 | 5 / 7 | |
| 0.6.1 | 5 / 7 | |
| 0.6.0 | 5 / 7 | |
| 0.5.2 | 5 / 7 | |
| 0.5.1 | 5 / 7 | |
| 0.5.0 | 5 / 7 | |
| 0.4.4 | 5 / 7 | |
| 0.4.3 | 5 / 7 | |
| 0.4.2 | 5 / 7 | |
| 0.4.1 | 5 / 7 | |
| 0.4.0 | 5 / 7 | |
| 0.3.11 | 5 / 7 | |
| 0.3.10 | 5 / 7 | |
| 0.3.9 | 5 / 7 | |
| 0.3.8 | 5 / 7 | |
| 0.3.7 | 5 / 7 | |
| 0.3.6 | 5 / 7 | |
| 0.3.5 | 5 / 7 | |
| 0.3.4 | 5 / 7 | |
| 0.3.3 | 5 / 7 | |
| 0.3.2 | 5 / 7 | |
| 0.3.1 | 5 / 7 | |
| 0.3.0 | 5 / 7 |
v0.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.