fin-pipl@1.0.0
CAUTION· static onlyPublisher claims: "金融行业个人信息保护（PIPL）合规检查工具。 基于《个人信息保护法》《个人金融信息保护规范》(JR/T 0171)、 《金融数据安全 数据安全分级指南》(JR/T 0197) 等行业法规， 提供银行、证券、保险、支付四大场景的合规评估。 Use when: 需要进行金融行业PIPL合规自查、 个人金融信息保护评估、金融数据安全分级检查、 金融产品营销合规检查、金融自动化决策合规评估。 🎉 v1.0.0 首发： - 📋 20+ 金融场景专属检查项 - 🏦 覆盖银行/证券/保险/支付四大业务 - 📊 支持 Markdown / JSON / HTML 多格式报告 - 🔒 纯本地运行" 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-10 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 1,391 lines in 12 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 wwumit: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.