typed-rest-client
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding in ntlm.js is standard NTLM protocol handling (parsing server challenge nonce from www-authenticate header). Legitimate and stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): vsonline mass-production signal reflects Microsoft's Azure DevOps toolchain publishing pattern, not spam. Short README is cosmetic. Legitimate Microsoft package with 45 versions and 9+ year history. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 5 / 9 | |
| 2.3.1 | 5 / 9 | |
| 2.3.0 | 5 / 9 | |
| 2.2.0 | 5 / 9 | |
| 2.1.0 | 5 / 9 | |
| 2.0.2 | 5 / 9 | |
| 2.0.1 | 5 / 9 | |
| 2.0.0 | 5 / 9 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.