Network

Scanner Network

Local scanner roles. Real Devnet attestations. Honest trust boundaries.

Solana DevnetConnected

0

Active Nodes

0

Registered Nodes

5

Total Attestations

5

Resolved Scans

How It Works

What this deployment actually does. Solana anchoring is optional and no independent scanner operators exist.

  1. Local scanner roles

    Three analytical modules run under one operator identity. What they inspect is fixed by code, not by a registry.

    0 independent nodes
  2. Package inspection

    The published tarball is checked for install scripts, obfuscation and integrity, alongside OSV advisories. Code is never executed.

    Active
  3. Signed findings & consensus

    Each role signs its findings with Ed25519. A deterministic policy returns ALLOW, REVIEW or BLOCK — there is no override flag.

    Active
  4. Optional Solana Devnet anchor

    A commitment hash can be written to Solana Devnet so anyone can confirm the evidence has not changed. This is not malware detection.

    Optional

Scanner Roles

Local analytical scanner roles signing verdicts on one machine, plus any independently registered nodes (currently zero).

No independently registered scanner nodes

The node registry is empty on this deployment. Scanners appear here with their identity and scan count once they register.

Latest Consensus Activity

Verdicts signed by three local scanner roles under one operator.

PackageVerdictSigned byTime
chalkallow3
is-oddallow3
nanoidallow3
lodashreview3
is-numberallow3