← Home

@api.global/typedrequest

npm
10
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

TypeScriptAPI RequestsHTTPTyped ProgrammingRequest RoutingResponse HandlingVirtual StreamsAsynchronousNetwork CommunicationServer CommunicationAPI Integration

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@push.rocks/lik AI (dependencies): Part of the publisher's own @push.rocks ecosystem; consistent across versions. ai
dependencies unvetted-dep:@push.rocks/smartdelay AI (dependencies): Part of the publisher's own @push.rocks ecosystem; consistent across versions. ai
semgrep semgrep:new-function-constructor AI (semgrep): Fires in bundled output; pattern consistent with template engine string interpolation, not dynamic code execution of external input. ai
semgrep semgrep:base64-decode AI (semgrep): Fires in bundled output alongside string processing utilities; no evidence of payload hiding or exfiltration. ai
phantom-deps phantom-dep:@push.rocks/webstream AI (phantom-deps): Declared as runtime dep and referenced in config; phantom-dep heuristic false positive for this package. ai

Versions (showing 10 of 10)

Version Deps Published
4.0.0 9 / 8
3.3.1 9 / 8
3.3.0 9 / 8
3.2.7 9 / 8
3.2.6 9 / 8
3.2.5 9 / 8
3.2.2 9 / 8
3.2.1 9 / 8
3.2.0 9 / 8
3.1.11 9 / 8

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.3.1

1 finding
LOW No provenance attestation provenance

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

v3.3.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.

v3.2.7

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.

v3.2.6

1 finding
LOW No provenance attestation provenance

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

v3.2.5

1 finding
LOW No provenance attestation provenance

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

v3.2.2

1 finding
LOW No provenance attestation provenance

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

v3.2.1

1 finding
LOW No provenance attestation provenance

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

v3.2.0

1 finding
LOW No provenance attestation provenance

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

v3.1.11

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.