Notary record

plyr@3.8.4

npm · checked 21 Oct 2026, 23:04 UTC · checker 2026-10-19.2 · log index 896

Record issued 21 Oct 2026

Issued 21 Oct 2026, 23:04 UTC · plyr@3.8.4 · 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.

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

plyr has no install step of its own.

1 of its 5 dependencies run one:

  • core-js@3.51.0postinstall

What the install steps reached

No install step reached anything we watch.

Programs
node
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 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

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

Show all 5
  • core-js@3.51.0
  • custom-event-polyfill@1.0.7
  • loadjs@4.3.0
  • rangetouch@2.0.1
  • url-polyfill@1.1.14

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-21T23:04:46Z
contentSha256
9ec5b3ec3573adbbc173b00c55f3791b983722823f11784a7433b35acd51d2d6
contentSizeBytes
1372760 (1.3 MB)
outputSha256
7b6d4fa90524065e3ad53f66eecaeacd200f7c492c46d7c4e38918a96b4298f0
log index
896

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

Inclusion proofCheckpointKey list

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