Nothing comes ashore until it's watched

An unknown package → held in isolation → its behaviour sheet.

$
t+000 msharness.startfork 5042 · block 1,204,118
t+184 mstool.discover12 tools
t+392 msnetwork.egressNOT YET RUN
t+648 msfile.readNOT YET RUN
t+902 mssignature.authNOT YET RUN
t+1,284 msallowance.askNOT YET RUN
Sends data outNOT YET RUN
Reads sensitive pathsNOT YET RUN
Signs payment authorizationsNOT YET RUN
Requests allowancesNOT YET RUN
pinned hash pending · fork block 1,204,118 · harness v0.1.0Open the sheet →

EGRESS TRACE

ISOLATIONsome-mcp-server@1.2.0NOT YET RUNegress hostpending run0 B256 B512 B1 KB

THE LATEST FIVE SHEETS

PACKAGEVERSIONSENDSREADSSIGNSALLOWSBLOCK
› 12 packages filed · 18 runs filed · fork block 1,204,118$QUARANTINE — CA drops at launchBUY → ARGUS

A public roll, pinned to exact code

Every filed row names one package version, one tarball hash, one fork block, and the four behaviours observed during its run.

HARBOUR ARRIVALS (TOP DOWN)ISOLATION ANCHORAGEBERTH 1BERTH 2BERTH 3BERTH 4BERTH 50 B256 B512 B1 KB
Sources: registry.npmjs.org · api.npmjs.org · registry.modelcontextprotocol.io · Arc RPC rpc.mainnet.arc.io · USDC 0x3600…0000