dunbars-number@1.0.6
CAUTIONPublisher claims: "Activate when: team headcount is approaching or crossing 150 (or 50, or 500); someone says "coordination is getting harder," "we lost the startup feel," or "we don't know who does what anymore"; deciding whether to split a team, open a new office, or add a management layer. Do NOT activate when: group is well below 50 and problems are clearly interpersonal; core issue is incentive misalignment rather than group size (use principal-agent instead). More: deciqai.com/c/dunbars-number" 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. 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 findings across 259 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.