All static findings were adjudicated as false positives. The high env_access hits are placeholder API_KEY examples and Secret Manager guidance, while the external command hits are Markdown CLI examples rather than executable code. No evidence found for prompt injection, exfiltration intent, or hidden command execution.
All static findings were adjudicated as false positives. The high env_access hits are placeholder API_KEY examples and Secret Manager guidance, while the external command hits are Markdown CLI examples rather than executable code. No evidence found for prompt injection, exfiltration intent, or hidden command execution.
Static analysis flagged a critical combination of commands, network references, and secret terms, but review found documentation-only Markdown with no executable code, obfuscation, prompt injection, or data exfiltration. Most static hits are false positives from Markdown backticks, prose, or official Firebase examples. Risk remains medium because the skill guides agents through Firebase CLI commands that can deploy, delete, or change cloud resources and manage secrets.
The skill documents Firebase CLI commands for deployment, backend deletion, rollout creation, backend creation, and secret access. These are legitimate App Hosting workflows, but they can change or delete Firebase resources if run without clear user approval.
The commands are plainly documented and include deploy, delete, create, and rollout operations. They are legitimate Firebase commands, but the operational impact is real.
Secret Handling Workflow Requires User Confirmation
The skill includes App Hosting secret commands and examples using API_KEY values. This is expected for Firebase App Hosting, but agents must avoid exposing secret values in logs, commits, prompts, or generated files.
The files clearly describe secret creation and local secret overrides. The guidance is not malicious, but mishandling these workflows could expose credentials.
Static false positives ignored (3)
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.
Markdown Backtick Command Alerts Are Mostly False Positives
The static analyzer labeled many Markdown backtick snippets as Ruby or shell backtick execution. The reviewed files contain documentation and fenced examples, not executable Ruby code or dynamic shell evaluation.
The cited locations are Markdown headings, inline code, or fenced examples. No file contains Ruby code, eval behavior, or shell interpolation logic.
Static analysis reported weak cryptographic algorithm blockers, but the cited lines are prose or configuration guidance. No evidence found of MD5, SHA1, insecure cipher use, or custom cryptography in the reviewed files.
The cited lines do not contain cryptographic APIs or algorithm names. They describe Firebase App Hosting and local emulator configuration.
The hardcoded URL points to the official Firebase Console billing page, and the configuration line flagged as network access is an environment availability value. No evidence found of outbound HTTP requests or data transmission code.
The only real URL is an official Firebase Console link for plan setup. The other cited line is the word RUNTIME in a YAML example, not a Python HTTP library.
All 75 static findings are false positives. The skill contains only documentation and reference materials describing Firebase CLI commands and configuration patterns. No actual code execution, credential access, or network requests occur. The detected patterns are markdown documentation examples, not executable code.
4
Files scanned
230
Lines analyzed
3
Review items
3
False positives ignored
Static false positives ignored (3)
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.
Static analyzer flagged `npx -y firebase-tools@latest` commands in markdown as Ruby/shell backtick execution. This is a documentation/reference skill that describes CLI commands. The backticks indicate code formatting in markdown, not actual execution. No command injection vulnerability exists.
Pattern matches CLI command examples in markdown documentation, not executable code with user-controlled input.
Static analyzer flagged https://console.firebase.google.com/project/_/overview URL as hardcoded URL. This is documentation pointing users to Firebase Console for billing plan upgrade. No network request is made by the skill.
Static URL reference in documentation, not an actual network call from the skill.
Static analyzer flagged API_KEY variable names as generic API/secret keys. These are placeholder examples in YAML configuration documentation showing how to configure environment variables. No actual secrets are accessed.
Placeholder variable names in configuration examples, not actual secret access.