No prompt injection, malicious network behavior, or data-exfiltration intent was found. Most external-command and blocker findings are false positives from markdown formatting, JavaScript template literals, comments, or PDF field identifiers; the confirmed findings are expected local filesystem reads and writes used for PDF processing.
12
Files scanned
1,909
Lines analyzed
28
Review items
0
False positives ignored
Capability review items (25)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
with open(output_file, 'w', encoding='utf-8') as f:
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
with open(f"chunk_{start_idx//chunk_size}.pdf", "wb") as output:
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The shipped script writes output JSON or PDF data to a command-line path. This is intended functionality, but it is real local file write capability and can overwrite existing files.
The shipped script writes output JSON or PDF data to a command-line path. This is intended functionality, but it is real local file write capability and can overwrite existing files.
The shipped script writes output JSON or PDF data to a command-line path. This is intended functionality, but it is real local file write capability and can overwrite existing files.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The batch-processing example enumerates PDF files in a user-supplied directory with glob. This is legitimate for PDF batching, but it can access more local files than intended if scoped poorly.
No prompt injection, malicious network behavior, or data-exfiltration intent was found. Most external-command and blocker findings are false positives from markdown formatting, JavaScript template literals, comments, or PDF field identifiers; the confirmed findings are expected local filesystem reads and writes used for PDF processing.
12
Files scanned
1,909
Lines analyzed
28
Review items
0
False positives ignored
Capability review items (25)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The reference example reads local PDF files from disk. This is expected for PDF processing, but it is real filesystem access that could expose unintended files if paths are chosen poorly.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
with open(output_file, 'w', encoding='utf-8') as f:
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
with open(f"chunk_{start_idx//chunk_size}.pdf", "wb") as output:
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The shipped script writes output JSON or PDF data to a command-line path. This is intended functionality, but it is real local file write capability and can overwrite existing files.
The shipped script writes output JSON or PDF data to a command-line path. This is intended functionality, but it is real local file write capability and can overwrite existing files.
The shipped script writes output JSON or PDF data to a command-line path. This is intended functionality, but it is real local file write capability and can overwrite existing files.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The guide or reference example writes generated PDF, text, image, or JSON output to local paths. This is expected behavior, but it can overwrite files or create outputs in unintended locations.
The batch-processing example enumerates PDF files in a user-supplied directory with glob. This is legitimate for PDF batching, but it can access more local files than intended if scoped poorly.
No malware, data exfiltration, or prompt injection evidence was found in the reviewed files. Most static hits are Markdown fences, JavaScript template literals, comments, documentation URLs, or expected PDF examples. Three helper scripts write to caller-provided output paths, so users should control destinations and avoid accidental overwrite.
12
Files scanned
1,909
Lines analyzed
6
Review items
0
False positives ignored
Capability review items (3)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
The script writes extracted field metadata to json_output_path supplied on the command line without path restriction. This intended output can overwrite a local file if invoked with an unsafe path.
The script writes the completed PDF to output_pdf_path supplied on the command line without path restriction. This intended output can overwrite a local file if invoked with an unsafe path.
The script writes an annotated PDF to output_pdf_path supplied on the command line without path restriction. This intended output can overwrite a local file if invoked with an unsafe path.
Static analysis reported many high-risk patterns, but review found them to be false positives from Markdown examples, comments, and sample data. The only real concern is expected filesystem access for reading PDFs and writing user-selected outputs. No evidence found of prompt injection, credential access, network exfiltration, or malicious command execution.
TRUE_POSITIVE: Helper scripts write JSON, image, and PDF outputs to paths supplied by the user. This is expected for PDF processing.
The write operations are direct and easy to verify. Risk is low because output paths are explicit CLI arguments for document processing.
Static false positives ignored (4)
These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.
FALSE_POSITIVE: Command examples appear in Markdown code blocks and inline instructions. They document standard PDF tools and are not executed by the skill.
The cited locations are Markdown examples for qpdf, pdftotext, pdfimages, and helper scripts. The Python scripts do not invoke shell commands.
FALSE_POSITIVE: High-severity keyword matches occur in PDF examples, test data, and benign command text. No cryptographic logic or C2 behavior is present.
The cited lines contain sample fields, file names, or PDF commands. They do not implement encryption, hashing, callbacks, or remote control.
Prompt Injection Review Found No Malicious Override
FALSE_POSITIVE: The skill contains workflow instructions for PDF forms. No text asks reviewers to skip analysis, lower risk, or ignore system instructions.
The wording is imperative, but it stays within the PDF form workflow. It does not target the marketplace evaluator or security process.
Static analysis detected 219 patterns across 12 files, but all are false positives. The 'external_commands' are markdown documentation code blocks, not executable code. 'Weak cryptographic algorithm' warnings are from test files using MD5 for non-security test data generation. 'C2 keywords' and 'system reconnaissance' are CLI argument parsing and legitimate system calls. The skill performs legitimate PDF processing using Python libraries (pypdf, pdfplumber, reportlab). Low risk due to filesystem operations and external tool dependencies (poppler-utils, qpdf) that require user-provided file paths.
12
Files scanned
1,909
Lines analyzed
5
Review items
0
False positives ignored
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Scripts write output PDF and JSON files to disk. User controls file paths via CLI arguments, minimizing risk.
Confirmed file write operations in Python scripts using open() with user-provided paths. Low risk because paths are CLI arguments, not user input from untrusted sources.
Documentation references external CLI tools (qpdf, pdftotext, pdfimages) that execute shell commands. These are documented usage patterns, not embedded malicious code.
Documentation shows legitimate use of standard PDF utilities (poppler-utils, qpdf). Commands are examples for users to run manually, not automated execution.