Notary record

redis-smq@10.1.2

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 20:22 UTC · redis-smq@10.1.2 · 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

redis-smq 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

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

Show all 36
  • @isaacs/fs-minipass@4.0.1
  • asynckit@0.4.0
  • axios@1.13.5
  • bluebird@3.7.2
  • call-bind-apply-helpers@1.0.2
  • chownr@3.0.0
  • combined-stream@1.0.8
  • commander@14.0.2
  • cron-parser@5.4.0
  • delayed-stream@1.0.0
  • dunder-proto@1.0.1
  • es-define-property@1.0.1
  • es-errors@1.3.0
  • es-object-atoms@1.1.2
  • es-set-tostringtag@2.1.0
  • follow-redirects@1.16.1
  • form-data@4.0.6
  • function-bind@1.1.2
  • get-intrinsic@1.3.0
  • get-proto@1.0.1
  • gopd@1.2.0
  • has-symbols@1.1.0
  • has-tostringtag@1.0.2
  • hasown@2.0.4
  • lodash@4.17.23
  • luxon@3.7.2
  • math-intrinsics@1.1.0
  • mime-db@1.52.0
  • mime-types@2.1.35
  • minipass@7.1.3
  • minizlib@3.1.0
  • proxy-from-env@1.1.0
  • redis-smq-common@10.1.2
  • tar@7.5.12
  • uuid@13.0.0
  • yallist@5.0.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
nothing_runs
verdict
manual_review
reasonCode
no_install_steps
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T20:22:52Z
contentSha256
a5e60a33226f1ac5cecee8e4c2a7b8de7621a26cadbcba4fba885b873ecc73e4
contentSizeBytes
429426 (419 KB)
log index
297

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

Inclusion proofCheckpointKey list

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

redis-smq@10.1.2: nothing runs at install. Kenwea notary | Kenwea Protocol