t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
6.5sfilesystemread ~/.npmrc
6.5sfilesystemread ~/.npm/_logs · ~/.npm/_cacache/index-v5/eb/f2/4d9fbfab6fca3fda4769eb74ca5485060425eb77a471fdd320e31ccd2437 · ~/.npm/_cacache/index-v5/d1/90/88de0ceb3bd9be994a6cefb480498ffb097f0f33a19e83cc7ce019ee82e7 · ~/.npm/_cacache/index-v5/dd/6e/bce38caf63982c22edfa4ade01b8c45a3dd89b43c50398b9b8b1769b7865 · ~/.npm/_cacache/index-v5/81/c2/efb20078489e457d93f09ca90387e55a4b73cb7572c80bc6b5935474ce29 · ~/.npm/_cacache/index-v5/16/d9/2de0c348847aa461989bae22a2083fd4a9da438b9768631321b66b5e3455 outside project
6.5sfilesystemwrote ~/.npm/_cacache/tmp/ca036b6d · ~/.npm/_cacache/index-v5/eb/f2/4d9fbfab6fca3fda4769eb74ca5485060425eb77a471fdd320e31ccd2437 · ~/.npm/_cacache/tmp/e8471858 · ~/.npm/_cacache/tmp/ed11f99e · ~/.npm/_cacache/tmp/50dfa0ab · ~/.npm/_cacache/index-v5/1c/bb/055a37d23dc7db81e96a1903c792d9ef7ee8ca5c503d2fd4e272b2a26ad4
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5snetworkCONNECT tcp://registry.npmjs.org:443
6.5sprocessexec /usr/local/bin/npm
6.5sprocessexited 243: npm error A complete log of this run can be found in: /tmp/ks-detonate-0jGuri/setup/home/.npm/_logs/2026-11-18T22_31_34_726Z-debug-0.log
6.5sprocessscript backend runs setup only
6.5sprocessscript backend runs setup only
11sprocesssecond launch, clock +45 days, CI unset
16sfilesystemread ~/.npmrc
16sfilesystemread ~/.npm/_logs · ~/.npm/_cacache/index-v5/eb/f2/4d9fbfab6fca3fda4769eb74ca5485060425eb77a471fdd320e31ccd2437 · ~/.npm/_cacache/content-v2/sha512/da/a0/ffd3af6a5aa1111e327f82f4df0fc662b05dcf17d374c2174b4dc2be33382be3fdaa2502977942009f4b76bc5acc2e22a92450b77dc83cdb8ac41b86d0f9 · ~/.npm/_cacache/index-v5/87/f4/0bc3fc4a26f7ef53a3fc04ced3452575da71921a9edc2f271d9ad17ec136 · ~/.npm/_cacache/index-v5/6d/4b/a55fb9e932d82cab6b4eea46b02e4c7ec424a55572dcc2a6a706bf137b12 · ~/.npm/_cacache/index-v5/d1/90/88de0ceb3bd9be994a6cefb480498ffb097f0f33a19e83cc7ce019ee82e7 outside project
16sfilesystemwrote ~/.npm/_cacache/tmp/363a9f1d · ~/.npm/_cacache/index-v5/eb/f2/4d9fbfab6fca3fda4769eb74ca5485060425eb77a471fdd320e31ccd2437 · ~/.npm/_cacache/tmp/37ba6c73 · ~/.npm/_cacache/tmp/c01b9747 · ~/.npm/_cacache/tmp/546ca0ab · ~/.npm/_cacache/tmp/9b497406
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16snetworkCONNECT tcp://registry.npmjs.org:443
16sprocessexec /usr/local/bin/npm
16sprocessexited 243: npm error A complete log of this run can be found in: /tmp/ks-detonate-0jGuri/later/home/.npm/_logs/2027-01-02T22_31_46_141Z-debug-0.log
Instructions loaded
≈2,280 tok
1 file · 3 in bundle
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.