90/ 100
No threats observedNo threats observed: The observed run produced no behaviour or code findings that changed the score. Scanned 23 Oct 2026.
Score
90 / 100Nothing was taken off for what the code did or what running it showed.
What it did
232 events in 42.2sNetwork
nothing real left the machineShow all 200 calls
Luna's report
No behaviour or code findings changed the score. Pin the scanned version. The most important limit is behaviour outside the observed install and entry windows.
We installed the package and ran its entry point in a throwaway sandbox, and scanned the code used by those paths. The run completed with an observed record.
What it ran
Jev's answers
answered from the evidenceShow all 5 answers
package.jsonShow all 3 answers
Not verified
Behaviour outside the observed install and entry windows
Code paths not triggered by install or the entry point
Show all 6 items
Payloads gated on calendar dates past the accelerated clock window, or on hosts that need real responses
A malware record exists for a dependency this run never installed: fsevents 1.2.2 (MAL-2023-462), macOS only, dev lockfile only (repo install, not package users), not installed in this run
Dev dependencies: install scripts run (0 packages), other code not executed (602 packages)
fsevents 1.2.2: macOS-only, flagged from its malware record, not run in this sandbox
Reputation
Shown apart from the code and behaviour findings.