Security audit

oss-format

Security checks for vulnerabilities and agentic risk

Overview

This is a documentation-formatting guide for open source repositories, with no hidden execution, persistence, or data-handling behavior found.

Install this if you want strong Tencent-style open source documentation formatting rules. Review generated LICENSE, SECURITY, Code of Conduct, and GitHub template changes before committing or publishing, especially if your project has its own language or governance policy.

A.I.G

Vulnerability Patterns

Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (1)

Natural-Language Policy Violations

Medium

Category: Not specified by scanner
Confidence: 95% confidence
Finding: Line L033 states '正式文档 100% 英文' as a blanket rule, and line L090 reinforces that SECURITY/CoC in Chinese repositories should still be written in English. This is a natural-language locale policy constraint that forces a specific language without user choice or a clearly bounded compliance justification.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.