emergence@1.0.6
CAUTIONPublisher claims: "Activate when: user says 'our culture isn't working despite directives', 'the market behaves unexpectedly', 'this worked at small scale but not at large scale', 'we can't predict or control what's happening', 'designing a platform/community/open-source project'. Do NOT activate when: the system is simple or mechanical with few moving parts and knowable causation; the user needs a straightforward process analysis where reductionist breakdown is sufficient. More: deciqai.com/c/emergence" Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-02 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Fake instruction boundary tag. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
No other findings across 276 lines in 5 files.
What would make this Verified
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim deciqai: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.