Notary record

loadtest@8.2.1

npm · checked 21 Oct 2026, 21:38 UTC · checker 2026-10-19.2 · log index 585

Record issued 21 Oct 2026

Issued 21 Oct 2026, 21:38 UTC · loadtest@8.2.1 · 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. Loading it once, as an application would, touched nothing we watch either.

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

loadtest has no install step of its own.

3 of its 30 dependencies run one:

  • bufferutil@4.1.0install
  • utf-8-validate@5.0.10install
  • es5-ext@0.10.64postinstall

What the install steps reached

No install step reached anything we watch.

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

It reached nothing we watch.

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

Dependencies

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

Show all 30
  • agent-base@4.3.0
  • agentkeepalive@2.2.0
  • bufferutil@4.1.0
  • confinode@2.1.1
  • d@1.0.2
  • debug@2.6.9
  • debug@3.2.7
  • es5-ext@0.10.64
  • es6-iterator@2.0.3
  • es6-promise@4.2.8
  • es6-promisify@5.0.0
  • es6-symbol@3.1.4
  • esniff@2.0.1
  • event-emitter@0.3.5
  • ext@1.7.0
  • https-proxy-agent@2.2.4
  • is-typedarray@1.0.0
  • ms@2.0.0
  • ms@2.1.3
  • next-tick@1.1.0
  • node-gyp-build@4.8.4
  • quick-lru@5.1.1
  • stdio@0.2.7
  • testing@3.1.0
  • type@2.7.3
  • typedarray-to-buffer@3.1.5
  • utf-8-validate@5.0.10
  • websocket@1.0.35
  • yaeti@0.0.6
  • yaml@1.10.3

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-21T21:38:26Z
contentSha256
7830574a544349f0ffd77a94481aa0591bec3777905708f5d4f4114a6f72aff8
contentSizeBytes
114228 (112 KB)
outputSha256
91c73d6f05cbdc9bf77e47e584343034cf07d8b132d6d9bce10f2cee9705bc07
log index
585

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

Inclusion proofCheckpointKey list

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

loadtest@8.2.1: quiet at install. Kenwea notary | Kenwea Protocol