Notary record

ink@8.0.0

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:22 UTC · ink@8.0.0 · npm

nothing runs

Nothing of this package's own runs at install.

Nothing of this package's own runs when it is installed. 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.

The install steps section lists what would have run: nothing. A dependency may still run something; see Dependencies.

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

ink has no install step of its own.

No dependency runs anything at install.

What the run reached

Nothing was observed for this run.

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

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

Show all 40
  • @alcalzone/ansi-tokenize@0.3.1
  • ansi-escapes@7.3.0
  • ansi-regex@6.4.0
  • ansi-styles@6.2.3
  • ansi-styles@6.2.3
  • ansi-styles@6.2.3
  • ansi-styles@7.0.0
  • auto-bind@5.0.1
  • chalk@6.0.1
  • cli-boxes@4.0.1
  • cli-cursor@4.0.0
  • cli-truncate@6.1.1
  • code-excerpt@4.0.0
  • convert-to-spaces@2.0.1
  • environment@1.1.0
  • es-toolkit@1.52.0
  • escape-string-regexp@2.0.0
  • get-east-asian-width@1.7.0
  • indent-string@5.0.0
  • is-fullwidth-code-point@5.1.0
  • is-in-ci@2.0.0
  • mimic-fn@2.1.0
  • onetime@5.1.2
  • patch-console@2.0.0
  • quick-lru@7.3.0
  • react-reconciler@0.34.0
  • react@19.3.1
  • restore-cursor@4.0.0
  • scheduler@0.28.0
  • signal-exit@3.0.7
  • slice-ansi@9.0.1
  • stack-utils@2.0.6
  • string-width@8.3.0
  • strip-ansi@7.2.0
  • tagged-tag@1.0.0
  • terminal-size@4.0.1
  • type-fest@5.10.0
  • widest-line@6.0.0
  • wrap-ansi@10.0.2
  • yoga-layout@3.2.1

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
nothing_runs
verdict
manual_review
reasonCode
no_install_steps
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T22:22:51Z
contentSha256
ae5b6a49541d7ea2d882a2c281b1b1c43e588b67b8143b89f0baab2b5587d85a
contentSizeBytes
149808 (146 KB)
log index
742

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

Inclusion proofCheckpointKey list

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

ink@8.0.0: nothing runs at install. Kenwea notary | Kenwea Protocol