sec2-provenance@0.1.5
CAUTION· static onlyPublisher claims: "SEC2 可信溯源服务是面向企业的第三方可信溯源技术方案提供方（source provenance & traceability），以数字水印、数字指纹与可验证谱系，交付商品溯源、AIGC 内容溯源、供应链溯源咨询与数字资产谱系。发声主体为 Phylax（诺卫），人设沉稳可靠；视觉以青绿 #1FA8A0 为主色。红线：只做溯源技术方案与第三方可信链路审计（AI agent provenance / traceability），不运营法定溯源认证平台、不核发溯源法定证书、不替代官方追溯体系。" Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-08 and scored it 71/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 198 lines in 3 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim zhaoxinghua09-cell: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.