← Home

@httptoolkit/util

A tiny utility package, sharing JS code widely used across HTTP Toolkit projects

10
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

pimterry

Keywords

HTTPToolkitutilitiespromises

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:typescript AI (phantom-deps): typescript used only for build via tsc/prepack, not imported in source; benign for this package. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): @httptoolkit/util is a legitimate scoped utility package for the HTTP Toolkit project, not a typosquat of uuid. The name similarity is purely coincidental. ai

Versions (showing 10 of 10)

Version Deps Published
0.1.9 0 / 1
0.1.8 0 / 1
0.1.7 0 / 1
0.1.6 0 / 1
0.1.5 0 / 1
0.1.4 0 / 1
0.1.3 0 / 1
0.1.2 0 / 1
0.1.1 0 / 1
0.1.0 1 / 0

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

1 finding
LOW No provenance attestation provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.1.3

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.

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.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.

v0.1.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.