Incomplete referenced artifact analysis
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md bash scripts/fixtures/run_fixtures.sh # 离线三档一次跑完,末行自报档数与不合枚数
Security audit
Security checks for vulnerabilities and agentic risk
This skill coherently drafts source-linked reviews without running the reviewed code, with optional external parsing that users control.
Use local-only review for confidential material. Approve external parsing only for URLs or documents you intend to share, excluding embedded tokens or signed links. Prefer a reviewed installer version and immutable source revision, or copy the inspected files manually. The checker validates report structure, not whether another skill is safe; external service behavior was not verified.
Referenced artifact was not completely inspected
bash scripts/fixtures/run_fixtures.sh # 离线三档一次跑完,末行自报档数与不合枚数
The installation command invokes an unpinned npm CLI through npx and selects no immutable revision of the skill repository. Although this is a CLI rather than an MCP server, compromised upstream releases could execute code with the installing user's privileges; the documented read-only review workflow does not protect this installation step.
The recommended installation command leaves both the npx CLI version and the skill repository revision unpinned. This is not an MCP server reference, but it creates a real supply-chain exposure: a compromised CLI release could execute with the user's privileges, and mutable skill content could change after review.
Without declared permissions the skill's intent is opaque and cannot be validated.
The remote-review route sends target URLs to an external parsing service without warning that URLs can contain private repository identifiers, access tokens, or signed query parameters. Asking before spending does not establish informed consent to disclose that information, and testing the Bridge with a real local file also needs an explicit data-handling check.
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.