@seele00/seele
Browser UI and server runtime for Seele Codex
This report shows the evidence for @seele00/seele@0.1.81. 2 of 10 known versions are blocked or flagged. The newest version, 0.1.92, is flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiDirect inspection found a concrete, undocumented third-party callback mechanism in the shipped executable. No install hook is needed for the runtime data-exfiltration risk to activate.
Decision evidence
public snapshot- libexec/seele-server hard-codes an external Profuse callback URL.
- Binary symbols name profuse_callback and spawn_profuse_notification.
- Nearby runtime strings identify notification events and instance_id.
- The callback endpoint is undocumented in README and deployment scripts.
- package.json has no npm lifecycle hooks.
- Bootstrap and proxy actions require explicit CLI commands.
Source & flagged code
9 flagged · loading sourcePackage source references dynamic require/import behavior.
web/dist/assets/javascript-wDzz0qaB.jsView on unpkg · L1Native or WebAssembly artifact printable strings contain known collector or webhook infrastructure.
libexec/seele-serverView on unpkgFindings
Affected versions and remediation
This report applies to @seele00/seele@0.1.81.
The versions list below shows the verdict for each recorded version.
- Avoid installing @seele00/seele@0.1.81. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.