Notary record

docsify@5.0.0

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

Record issued 21 Oct 2026

Issued 21 Oct 2026, 21:20 UTC · docsify@5.0.0 · npm

unfinished

The check could not finish. This is not a pass.

The check could not finish (step_timed_out), so this is not a pass.

The trace shows what a step attempted. A quiet trace is evidence, not proof.

An unfinished check is not a pass. Nothing here says the package is quiet.

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

docsify runs this install step of its own:

  • postinstall

No dependency runs anything at install.

What the install steps reached

DNS
  • registry.npmjs.org
Requests
  • TLS to registry.npmjs.org:443 (1595 bytes sent, encrypted)
Programs
node, npx, opencollective-postinstall
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

No first import was recorded for this check.

Dependencies

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

Show all 7
  • common-tags@1.8.2
  • dexie@4.4.6
  • marked@18.1.1
  • medium-zoom@1.1.0
  • opencollective-postinstall@2.0.3
  • prismjs@1.30.0
  • tinydate@1.3.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
unfinished
verdict
manual_review
reasonCode
step_timed_out
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T21:20:32Z
contentSha256
79c7bbfae7da584690c21534fae18ef8c0de39823e6c2d801d23551228b02ef8
contentSizeBytes
880876 (860 KB)
outputSha256
5d13d0287ee6973c88b0605c9b4cfe7bb77d9490c729de28ee0478bd5f6c3c3f
log index
514

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

Inclusion proofCheckpointKey list

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