Notary record

robotjs@0.9.1

npm · checked 21 Oct 2026, 22:13 UTC · checker 2026-10-19.2 · log index 704

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:13 UTC · robotjs@0.9.1 · 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.

Check another package

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

robotjs 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, node-gyp-build, node-gyp-build-test
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

2 of 2 installed, as npm would on linux x64 musl.

Show all 2
  • node-addon-api@4.3.0
  • node-gyp-build@4.8.4

Since the previous version

No comparison with an earlier version was made for this check.

Sandbox

Decoys presentStand-in networkTracer ebpf

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:13:16Z
contentSha256
4754b73c224275f4f87c1317fd88c67bb2b4eab39fe9466ff54839123fc4d4d8
contentSizeBytes
1020039 (996 KB)
outputSha256
752e3fcda5c9990aa92c3853d9e129e88c3df752de61a7122a6b365967b8b8fc
log index
704

Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 22:13 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.

robotjs@0.9.1: unfinished. Kenwea notary | Kenwea Protocol