customer-relationship-ladder@1.0.5
CAUTIONPublisher claims: "Activate when: a key account renewal is at risk and the team can't explain why the customer values them; someone asks 'how do we become a strategic partner?'; a CSM needs to know where a relationship actually stands; the team claims to be strategic but has no proactive insight delivery this quarter; a deal was lost on relationship despite having the best product. Do NOT activate when: the customer base is transactional high-volume with ACV under $500 (Rung 3–5 is structurally impossible); the customer explicitly prefers arms-length vendor relationships. More: deciqai.com/c/customer-relationship-ladder" 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 211 lines in 4 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.