vscode-languageserver-textdocument
A simple text document implementation for Node LSP servers
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 |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): dbaeumer→vscode-bot org handoff, stable 1318d; legitimate Microsoft pipeline. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Microsoft org bot/team accounts; expected for official package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Individual devs replaced by org accounts; benign transfer. | ai | |
| provenance | missing-githead | AI (provenance): Secure-pipeline publish drops gitHead; no malicious signal. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.13 | 0 / 0 | |
| 1.0.12 | 0 / 0 | |
| 1.0.11 | 0 / 0 | |
| 1.0.10 | 0 / 0 | |
| 1.0.9 | 0 / 0 | |
| 1.0.8 | 0 / 0 | |
| 1.0.7 | 0 / 0 | |
| 1.0.6 | 0 / 0 | |
| 1.0.5 | 0 / 0 | |
| 1.0.4 | 0 / 0 | |
| 1.0.3 | 0 / 0 | |
| 1.0.2 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.0.10
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (dbaeumer) on 2023-04-19. It has since remained available on npm for 1187 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (dbaeumer) on 2023-01-16. It has since remained available on npm for 1280 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.
This version was published by a different npm account (vscode-bot) than the most recent previously approved version (dbaeumer) on 2022-12-09. It has since remained available on npm for 1318 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dbaeumer) than the most recent previously approved version (aeschli) on 2021-10-08, but dbaeumer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.1
2 findingsThis version was published by a different npm account (aeschli) than the most recent previously approved version (dbaeumer) on 2020-02-21. It has since remained available on npm for 2340 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.