Notary record

vtop@0.6.1

npm · checked 21 Oct 2026, 21:18 UTC · checker 2026-10-19.2 · log index 507

Record issued 21 Oct 2026

Issued 21 Oct 2026, 21:18 UTC · vtop@0.6.1 · npm

network

An install step tried to reach the network. Find out why before installing.

Loading it tried to reach the network (DNS registry.npmjs.org, TLS to registry.npmjs.org:443 (1595 bytes sent, encrypted)), before your code called anything. Find out why before using it.

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

vtop has no install step of its own.

1 of its 26 dependencies run one:

  • husky@0.14.3install

What the install steps reached

No install step reached anything we watch.

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

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

DNS
  • registry.npmjs.org
Requests
  • TLS to registry.npmjs.org:443 (1595 bytes sent, encrypted)
Programs
free, node, npm, ps
Credentials read
No credential file or variable was opened.
Credentials sent
No decoy left the box.

Dependencies

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

Show all 26
  • balanced-match@1.0.2
  • blessed@0.1.81
  • brace-expansion@1.1.21
  • ci-info@1.6.0
  • commander@2.11.0
  • concat-map@0.0.1
  • drawille@1.1.0
  • fs.realpath@1.0.0
  • glob@7.1.2
  • husky@0.14.3
  • inflight@1.0.6
  • inherits@2.0.4
  • inpath@1.0.2
  • is-ci@1.2.1
  • minimatch@3.1.5
  • mute-stream@0.0.8
  • normalize-path@1.0.0
  • once@1.4.0
  • os-utils@0.0.14
  • path-is-absolute@1.0.1
  • pidof@1.0.2
  • read@1.0.7
  • strip-indent@2.0.0
  • sudo@1.0.3
  • use-strict@1.0.1
  • wrappy@1.0.2

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
network
verdict
manual_review
reasonCode
load_tried_network
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T21:18:23Z
contentSha256
b5247f3ccf06bfb0df27f91031ec4681e90cc0d1cdb85b067f5570b42e1ecfe5
contentSizeBytes
2774173 (2.6 MB)
outputSha256
8e89e6b597dbbd2063cefcc2b231df70ddeb2f843849fa0a212012f187acd965
log index
507

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

Inclusion proofCheckpointKey list

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

vtop@0.6.1: network at install. Kenwea notary | Kenwea Protocol