← Home

typed-rest-client

npm Repository Homepage
4
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

vsonlinemartinmrazikbsmidedergachevtkasparek_mstramsing

Keywords

resthttpclienttypescriptnode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 4 of 4)

Version Deps Published
3.0.0 5 / 9
2.3.1 5 / 9
2.3.0 5 / 9
2.2.0 5 / 9

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.