lwip@0.0.9
npm · checked 21 Oct 2026, 22:06 UTC · checker 2026-10-19.2 · log index 682
Record issued 21 Oct 2026
Issued 21 Oct 2026, 22:06 UTC · lwip@0.0.9 · npm
unfinished
The check could not finish. This is not a pass.
The check could not finish (install_step_failed), so this is not a pass.
The trace shows what a step attempted. A quiet trace is evidence, not proof.
An unfinished check is not a pass. Nothing here says the package is quiet.
Phases
This record does not state its phases one by one; npm records from checker 2026-11-03.1 and Python records from 2026-11-04.3 on do.
Install steps
lwip runs this install step of its own:
- install
No dependency runs anything at install.
What the install steps reached
No install step reached anything we watch.
- Programs
- node, node-gyp
- Credentials read
- No credential file or variable was opened.
- Credentials sent
- No decoy left the box.
- Looked for
- python, python3
The record keeps what all the install steps reached together; it does not say which step did which.
First import
No first import was recorded for this check.
Dependencies
7 of 7 installed, as npm would on linux x64 musl.
Show all 7
- async@2.6.4
- bindings@1.5.0
- decree@0.0.6
- file-uri-to-path@1.0.0
- lodash-node@2.4.1
- lodash@4.18.1
- nan@2.30.0
Since the previous version
No comparison with an earlier version was made for this check.
Sandbox
network=none; capabilities=all-dropped; rootfs=read-only; user=nobody; harness=separate-user
Signature and transparency log
- level
- unfinished
- verdict
- manual_review
- reasonCode
- install_step_failed
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T22:06:47Z
- contentSha256
- 55501bd9235e9ef86808e40040bb239bf3b9de336b64216210372c625455993f
- contentSizeBytes
- 3221457 (3.1 MB)
- outputSha256
- 762ff9bdf6ff5f75a5f2017e0300d5eeabcce5682504be61b7612fc1ced220e4
- log index
- 682
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 22:06 UTC
What this does and does not say
The claim is about the bytes, not the name.
The signature covers these exact bytes. Another version is another check.
A quiet trace is evidence, not proof.
Code that only runs later, when your app calls it, is out of reach.
A signature is not an endorsement.
It says what happened, not that the code is good.
Twenty checks an hour for each network address. When a limit is ours, the record says unfinished and names it.