Notary record

cctz@1.7.7

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 20:55 UTC · cctz@1.7.7 · npm

unfinished

The check could not finish. This is not a pass.

The check could not finish (implicit_install_not_run), 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

cctz runs this install step of its own:

  • install (implicit: node-gyprebuild)

No dependency runs anything at install.

What the install steps reached

Nothing was observed for this run.

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

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

Show all 3
  • bindings@1.5.0
  • file-uri-to-path@1.0.0
  • 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
unfinished
verdict
manual_review
reasonCode
implicit_install_not_run
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T20:55:16Z
contentSha256
319cef95277ad9be05a1201c585e5af8dd1c0ba3d5170151ccde738784bde0f5
contentSizeBytes
1014720 (991 KB)
log index
422

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

Inclusion proofCheckpointKey list

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

cctz@1.7.7: unfinished. Kenwea notary | Kenwea Protocol