qa-test-reporting@1.8.0
CAUTIONPublisher claims: "输出面向不同受众的测试报告——日报给团队同步进度、周报给项目经理、质量报告给管理层决策。当测试执行完成需要汇总结果、或者上级问"质量怎么样"的时候使用此技能。不同角色关心的数据不同:开发关心Bug明细,经理关心通过率和趋势,老板关心风险和发版决策。报告内容适配受众,关键指标量化呈现,风险区域必须单独成节并醒目标注。 触发场景:测试报告、日报、周报、迭代报告、报告模板、质量汇报、进度汇报、向管理层汇报测试进展时。 Use when the user asks about: writing test reports for different audiences — daily reports for the team, weekly reports for the PM, and quality summaries for management." 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-29 and scored it 69/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 other findings across 383 lines in 4 files.
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim kokxi: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.