request-light
Lightweight request library. Promise based, with proxy support.
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.
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed from individual MS employee (aeschli) to Microsoft's vscode-bot automation account — a well-known, trusted bot with 799 approved versions. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with Microsoft's move to bot-based publishing; no security concern for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Microsoft personnel and automation accounts (vscode-bot, microsoft1es, etc.); legitimate org restructuring. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers were MS/VS Code team members replaced by current MS accounts; routine access rotation. | ai | |
| provenance | no-provenance | AI (provenance): Microsoft/vscode-bot ecosystem package; lack of Sigstore provenance is a best-practice gap, not a security risk for this trusted publisher. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 0 / 12 | |
| 0.7.0 | 0 / 12 | |
| 0.6.0 | 0 / 12 | |
| 0.5.8 | 0 / 11 | |
| 0.5.7 | 0 / 11 | |
| 0.5.6 | 0 / 11 | |
| 0.5.5 | 0 / 11 | |
| 0.5.4 | 0 / 11 | |
| 0.5.3 | 0 / 11 | |
| 0.5.2 | 0 / 11 | |
| 0.5.1 | 0 / 11 | |
| 0.5.0 | 3 / 8 | |
| 0.4.0 | 3 / 3 | |
| 0.3.0 | 3 / 3 | |
| 0.2.5 | 3 / 3 | |
| 0.2.4 | 3 / 2 | |
| 0.2.3 | 3 / 2 | |
| 0.2.2 | 3 / 3 | |
| 0.2.1 | 3 / 3 | |
| 0.2.0 | 3 / 3 | |
| 0.1.0 | 3 / 1 | |
| 0.0.3 | 3 / 1 | |
| 0.0.2 | 3 / 1 | |
| 0.0.1 | 3 / 2 |
v0.8.0
2 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v0.6.0
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 than previous versions on 2022-11-03. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.