← Home

@whatwg-node/server

npm Repository Homepage

Fetch API compliant HTTP Server adapter

100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ardatantheguild-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:semver AI (typosquat): @whatwg-node/server is a legitimate HTTP server adapter with no relation to semver. The Levenshtein match is a false positive based on the unscoped package name fragment. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() is used inside a Proxy handler's get trap — the canonical pattern for transparent proxy delegation, not obfuscation. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a declared runtime dependency used implicitly by TypeScript-compiled output; this is expected behavior for TS packages. ai

Versions (showing 100 of 200)

Hide prereleases
Version Deps Published
0.8.3 3 / 0
0.8.2 3 / 0
0.8.1 2 / 0
0.8.0 2 / 0
0.7.7 2 / 0
0.7.6 2 / 0
0.7.5 2 / 0
0.7.4 2 / 0
0.7.3 2 / 0
0.7.2 2 / 0
0.7.1 2 / 0
0.7.0 2 / 0
0.6.7 2 / 0
0.6.6 2 / 0
0.6.5 2 / 0
0.6.4 2 / 0
0.6.3 2 / 0
0.6.2 2 / 0
0.6.1 2 / 0
0.6.0 2 / 0
0.5.11 2 / 0
0.5.10 2 / 0
0.5.9 2 / 0
0.5.8 2 / 0
0.5.7 2 / 0
0.5.6 2 / 0
0.5.5 2 / 0
0.5.4 2 / 0
0.5.3 2 / 0
0.5.2 2 / 0
0.5.1 2 / 0
0.5.0 2 / 0
0.4.17 2 / 0
0.4.16 2 / 0
0.4.15 2 / 0
0.4.14 2 / 0
0.4.13 2 / 0
0.4.12 2 / 0
0.4.11 2 / 0
0.4.10 2 / 0
0.4.9 2 / 0
0.4.8 2 / 0
0.4.7 2 / 0
0.4.6 2 / 0
0.4.5 2 / 0
0.4.4 2 / 0
0.4.3 2 / 0
0.4.2 2 / 0
0.4.1 2 / 0
0.4.0 2 / 0
0.3.0 2 / 0
0.2.0 2 / 0
0.1.2 2 / 0
0.1.1 2 / 0
0.1.0 2 / 0
0.0.6 2 / 0
0.0.5 2 / 0
0.0.4 2 / 0
0.0.3 2 / 0
0.0.2 2 / 0
0.0.1 2 / 0
0.10.19-alpha-20260407155020-afbfe22dd2ac0294de251b3046daddf4464c5857 5 / 0
0.10.19-alpha-20260407154422-6eedd27df15fb79b15fe0d1b7e474f3c271168fd 5 / 0
0.10.19-alpha-20260407154227-555157dbfce42ad79d9d7a83d2d9b47a8e29a65e 5 / 0
0.10.19-alpha-20260407153515-125740a25a9b6a1730a0627cb6e4324a5a258c37 5 / 0
0.10.19-alpha-20260407153259-4d793acfb257b53bfa9a2b18956a2b9004a511f0 5 / 0
0.10.19-alpha-20260407152503-92db393ca13ca7a418a470e8771416a5d488817d 5 / 0
0.10.19-alpha-20260407152120-17c4c40f1423f3ae728b7623626f7f108ceb2fa6 5 / 0
0.10.19-alpha-20260407151701-afc13dba5562037278f18055e80941c740b33ee8 5 / 0
0.10.19-alpha-20260407150639-7968dd6e5e8de473b2402f5e9490b94bc1815e20 5 / 0
0.10.19-alpha-20260407144444-e57d569e1b0a5dd50168a14be5a4a396c200d8d2 5 / 0
0.10.19-alpha-20260407135918-e11f8e4857ce4fe0da4131287f4f1841786ee7be 5 / 0
0.10.19-alpha-20260407135759-1de99a35e57921eac835fe10f993b2e22010e7e2 5 / 0
0.10.19-alpha-20260407135119-d94639eba0440cf5a490a2841d24339f8bca1454 5 / 0
0.10.19-alpha-20260407134358-73c6f60ac5c5685434c2d2893b9a40b7ce16dcb1 5 / 0
0.10.19-alpha-20260407134141-503b67387ac26cb7f27d18ec147672f7ee0aec7e 5 / 0
0.10.19-alpha-20260407133711-558aeb729b2e9749e93c37fbab91eef215e5512e 5 / 0
0.10.19-alpha-20260407121449-dd71a9a54bf50baa7f7e70ff40f229948a65a9e6 5 / 0
0.10.19-alpha-20260407121031-4f1a5fe30cfa665a9027acda3ce7a0ea9f756da2 5 / 0
0.10.19-alpha-20260407115946-1d59f48c12c192b27ea68089dc5214b2b3b6b447 5 / 0
0.10.19-alpha-20260407111544-3b62095163ce033b7810438230d08eadb5fabdfa 5 / 0
0.10.19-alpha-20260407111028-26ee53c8c3325afafb6a519f2c12c522eaccaf9d 5 / 0
0.10.19-alpha-20260402115041-e5e902ab45b0819e620e3961657d825b8381d83a 5 / 0
0.10.19-alpha-20260326221420-0f4c9f822126b6261080ec2d16157d23f5f5d233 5 / 0
0.10.19-alpha-20260326193620-079a2e4ab535fafb78f83d1d53e1256720737921 5 / 0
0.10.19-alpha-20260326192252-e3abf2c616574f20bde75832f7ec503e5dac3f46 5 / 0
0.10.19-alpha-20260326191616-463fbbd9ecddda9d9338f62b198dc6e1885e05de 5 / 0
0.10.19-alpha-20260326160322-f4867155884f9da53df7e70cf65331ff66c83233 5 / 0
0.10.19-alpha-20260326155831-3181dde8ff9fc03e8de933d469b3991d7a36865e 5 / 0
0.10.19-alpha-20260321231858-4e3a0cb982c0df09a50f3dc0e10ac80392df6d00 5 / 0
0.10.19-alpha-20260321225142-4a553df0f51d3cc24bda6ec9a3eb22d21d512d22 5 / 0
0.10.19-alpha-20260321215737-4b6a2e836dea5ddd4b7ffab547573307190f402c 5 / 0
0.10.19-alpha-20260321212014-14684ae886464dae84f22f7b6b567f6f2415f345 5 / 0
0.10.18-alpha-20260106205237-6541c9983a950711e7c0e2196f51e33fb0cd1ff0 5 / 0
0.10.18-alpha-20251204164651-10666707bffc27d1e49d3c44cde95d3bcbb9baa2 5 / 0
0.10.18-alpha-20251204164415-00350d4cd2bf8d146d84e8365456cae5354e0d36 5 / 0
0.10.18-alpha-20251204161910-2003e62893209e3fa3217923be080639992c9e3d 5 / 0
0.10.16-alpha-20251110204347-16d19b0f9727cc130885edd3d0d9a79139ac963a 5 / 0
0.10.16-alpha-20251110163100-4652b77de1cf710e75445db45d91cdf62127a39f 5 / 0
0.10.16-alpha-20251110161950-a399c572806c26a67ae5f1b3dbb21cac7461155a 5 / 0

v0.8.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.8.2

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.8.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.8.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.

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

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

v0.7.5

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.7.4

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.7.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.7.2

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

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

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

v0.6.5

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.6.4

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.6.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.6.2

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.6.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.6.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.

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

v0.5.10

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.5.9

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.5.8

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.5.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.

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

v0.5.5

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.5.4

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.5.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.5.2

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.5.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.5.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.

v0.4.17

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'semver' typosquat

Package name '@whatwg-node/server' is 1 edit(s) away from popular package 'semver'.

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.4.16

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.4.15

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.4.14

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.4.13

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.4.12

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.4.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.

v0.4.10

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.4.9

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.4.8

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.4.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.

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

v0.4.5

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.4.4

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.4.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.4.2

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.4.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.4.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.

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

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

v0.1.2

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

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

v0.0.5

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.0.4

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.0.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.0.2

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.0.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.