Notary record

bullmq@6.3.11

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:45 UTC · bullmq@6.3.11 · 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

bullmq has no install step of its own.

1 of its 10 dependencies run one:

  • msgpackr-extract@3.0.4install

What the install steps reached

No install step reached anything we watch.

Programs
node, node-gyp-build-optional-packages, node-gyp-build-optional-packages-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

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

Show all 10
  • @msgpackr-extract/msgpackr-extract-linux-x64@3.0.4
  • cron-parser@5.10.1
  • detect-libc@2.1.2
  • luxon@3.7.2
  • msgpackr-extract@3.0.4
  • msgpackr@2.1.0
  • node-abort-controller@3.1.1
  • node-gyp-build-optional-packages@5.2.2
  • semver@7.8.5
  • tslib@2.8.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
quiet
verdict
approved
reasonCode
ran_ok
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T22:45:50Z
contentSha256
d9c3d4ebeac0a6d8d015664ba16350e343a7713bb5407cb868ca6f0e50a79675
contentSizeBytes
540466 (528 KB)
outputSha256
4710768fc242699a2e0146bff6144cb26130863f9d11ae8b4503bca629bd1577
log index
822

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

Inclusion proofCheckpointKey list

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