@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, so a manually published version cannot be tied back to a reviewed commit.
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 89 of 89)
| Version | Deps | Published |
|---|---|---|
| 0.10.1 | 5 / 7 | |
| 0.10.0 | 5 / 7 | |
| 0.9.11 | 5 / 7 | |
| 0.9.9 | 5 / 7 | |
| 0.9.8 | 5 / 7 | |
| 0.9.7 | 5 / 7 | |
| 0.9.6 | 5 / 7 | |
| 0.9.5 | 5 / 7 | |
| 0.9.4 | 5 / 7 | |
| 0.9.3 | 5 / 7 | |
| 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 | |
| 0.2.12 | 5 / 7 | |
| 0.2.11 | 5 / 9 | |
| 0.2.10 | 5 / 9 | |
| 0.2.9 | 5 / 9 | |
| 0.2.8 | 5 / 9 | |
| 0.2.7 | 5 / 9 | |
| 0.2.6 | 5 / 9 | |
| 0.2.5 | 5 / 9 | |
| 0.2.4 | 5 / 9 | |
| 0.2.3 | 5 / 9 | |
| 0.2.2 | 5 / 9 | |
| 0.2.1 | 5 / 9 | |
| 0.2.0 | 5 / 9 | |
| 0.1.16 | 5 / 9 | |
| 0.1.15 | 5 / 9 | |
| 0.1.13 | 5 / 9 | |
| 0.1.12 | 5 / 9 | |
| 0.1.11 | 5 / 9 | |
| 0.1.10 | 5 / 9 | |
| 0.1.9 | 5 / 9 | |
| 0.1.8 | 5 / 9 | |
| 0.1.7 | 5 / 9 | |
| 0.1.6 | 5 / 9 | |
| 0.1.5 | 4 / 9 | |
| 0.1.4 | 4 / 9 | |
| 0.1.3 | 4 / 9 | |
| 0.1.2 | 4 / 9 | |
| 0.1.1 | 4 / 9 | |
| 0.1.0 | 4 / 9 |
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.