Notary record

qrcode@1.5.4

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:48 UTC · qrcode@1.5.4 · npm

nothing runs

Nothing of this package's own runs at install.

Nothing of this package's own runs when it is installed.

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

qrcode 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 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

27 of 28 installed, as npm would on linux x64 musl. The tree is not complete.

Show all 28
  • ansi-regex@5.0.1
  • ansi-styles@4.3.0
  • camelcase@5.3.1
  • cliui@6.0.0
  • color-convert@2.0.1
  • color-name@1.1.4
  • decamelize@1.2.0
  • dijkstrajs@1.0.3
  • emoji-regex@8.0.0
  • find-up@4.1.0
  • get-caller-file@2.0.5
  • is-fullwidth-code-point@3.0.0
  • locate-path@5.0.0
  • p-limit@2.3.0
  • p-locate@4.1.0
  • p-try@2.2.0
  • path-exists@4.0.0
  • pngjs@5.0.0
  • require-directory@2.1.1
  • require-main-filename@2.0.0
  • set-blocking@2.0.0
  • string-width@4.2.3
  • strip-ansi@6.0.1
  • which-module@2.0.1
  • wrap-ansi@6.2.0
  • y18n@4.0.3
  • yargs-parser@18.1.3
  • yargs@15.4.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:48:13Z
contentSha256
0c7274f0c299f39c2fddf54a2e0039b785977b0173c02d0b3f65fad68923e2b0
contentSizeBytes
50428 (49 KB)
log index
831

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

Inclusion proofCheckpointKey list

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