qianyuan-guard@1.0.2
CAUTIONPublisher claims: "Before building, debugging, or writing to production: check known pitfalls and reuse verified results. Skip for read-only queries. Call this IMMEDIATELY when you hit a failure you have never seen before, or when retrying the same tool is not making progress — returns whether other agents hit the same failure and what they did to fix it." 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-10-30 and scored it 70/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 309 lines in 2 files.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim alvinxiao2: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.