← Home

@api.global/typedserver

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

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

lossless

Keywords

TypeScriptstatic file servinglive reloadcompressiontyped requestsHTTP serverSSLcorsproxysitemapfeedsrobots.txtcompression (gzip, deflate, brotli)

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Publisher has strong track record (85 approved); likely CI environment change, not a takeover signal for this package. ai
semgrep semgrep:toplevel-fetch AI (semgrep): Fetch targets own /sw-dash/metrics endpoint in a dashboard component; not exfiltration. ai
semgrep semgrep:new-function-constructor AI (semgrep): Dynamic import shim pattern in bundled web code; standard technique, not arbitrary code exec from external input. ai
semgrep semgrep:base64-decode AI (semgrep): URL-safe base64 decode utility; no external input or payload hiding. ai
phantom-deps phantom-dep:@push.rocks/smartenv AI (phantom-deps): Declared dep used via config files; phantom-dep heuristic false positive for this package. ai

Versions (showing 2 of 2)

Version Deps Published
8.4.7 35 / 5
8.4.6 35 / 5

v8.4.7

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: lossless.

LOW No provenance attestation provenance

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

v8.4.6

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.