Notary record

edge-js@26.1.0

npm · checked 21 Oct 2026, 20:37 UTC · checker 2026-10-19.2 · log index 355

Record issued 21 Oct 2026

Issued 21 Oct 2026, 20:37 UTC · edge-js@26.1.0 · npm

quiet

Its install steps ran with decoy credentials in reach and touched nothing we watch.

Its install steps ran here, with decoy credentials in reach, and touched nothing we watch: no network, no credential files. That is evidence, not proof: code can wait for a different machine or run later, when it is used.

The trace shows what a step attempted. A quiet trace is evidence, not proof.

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

edge-js 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

It was imported once, as an application would, and exited 1.

It reached nothing we watch.

Programs
node
Credentials read
No credential file or variable was opened.
Credentials sent
No decoy left the box.

loading it exited 1; many libraries need configuration or a host to load, so this says little either way

Dependencies

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

Show all 2
  • edge-cs@npm:@agracio/edge-cs@1.3.7
  • nan@2.30.0

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
quiet
verdict
approved
reasonCode
ran_ok
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T20:37:24Z
contentSha256
411bafe66d7a067e2d695b1f10d764f4717e3f0fff7d80b8c5b587b3abb60688
contentSizeBytes
4931217 (4.7 MB)
outputSha256
eacf79dab87310afdcff7a5f2167e5942f2d54557983a4c19629b733e0f57d17
log index
355

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

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 20:37 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.

edge-js@26.1.0: quiet at install. Kenwea notary | Kenwea Protocol