qa-state-transition@1.8.0
CAUTIONPublisher claims: "系统化测试状态机的合法转换、非法转换、边界转换和并发转换场景。当业务对象经历了多种状态(如订单:待支付→已支付→已发货→已完成)、或者需要验证状态变化时的数据一致性时,应当使用此技能。最容易遗漏的是非法转换(业务不允许的操作如"已完成→待支付")和并发转换(同一订单同时被支付和取消)。每个状态转换需标注触发条件、前置状态、后置状态和验证点。 触发场景:状态测试、状态转换、状态机、状态流转、状态变更、状态覆盖、业务对象有多状态流转时。 Use when the user asks about: state machine testing — legal, illegal, boundary, and concurrent state transitions, and data consistency across them." 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 315 lines in 3 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.