carbon-emission-report-check-free@1.0.8
CAUTIONPublisher claims: "碳排放报告与活动数据逐格复算与勾稽(本免费版执行 6 项,另有 5 项完整档检查未执行且如实列出)。逐行复算 活动数据 × 排放因子 × 氧化率 = 排放量、分设施/分范围小计与合计对明细之和、范围二 万kWh/MWh/kWh/GJ 单位换算勾稽、同设施同年度同品种重复行、同品种排放因子不一致、必需字段空白与认不出格式检测,每条结论都引用原文行号与具体数字。缺必需列只报材料不足、绝不给结论。触发词包括 碳排放报告数据核对、排放报告复算、核查前自查、活动数据与排放量对不上。" 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-06 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 972 lines in 5 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
13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim chenqg618: 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.