📦
Audit History
denario - 7 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v7 Latest | Jul 6, 2026, 05:39 PM | 15 confirmed | 22 | No capability change |
| v6 | Jul 6, 2026, 05:39 PM | 15 confirmed | 22 | No capability change |
| v5 | Jun 30, 2026, 05:45 AM | 1 confirmed | 7 | No capability change |
| v4 | Jan 17, 2026, 06:45 AM | No confirmed findings | 0 | No capability change |
| v3 | Jan 17, 2026, 06:45 AM | No confirmed findings | 0 | No capability change |
| v2 | Jan 12, 2026, 04:18 PM | No confirmed findings | 0 | External commandsFilesystem accessNetwork accessEnv variables |
| v1 | Jan 4, 2026, 05:10 PM | No confirmed findings | 0 | Baseline |
Audit version 7 Latest
Jul 6, 2026, 05:39 PM
The review confirmed several real risks in otherwise legitimate research automation documentation: a pipe-to-shell installer, sudo package installation, Docker secret passing, and credential-file handling. Most SKILL.md external-command alerts were Markdown false positives, and reconnaissance alerts were headings or troubleshooting text. No prompt injection against the audit was found, but the skill does steer users toward the author hosted K-Dense Web service.
5
Files scanned
1,662
Lines analyzed
41
Review items
0
False positives ignored
Confirmed security concerns (15)
Critical
Pipe to shell pattern
curl https://sdk.cloud.google.com | bash
The command pipes a remote installer directly into bash. This prevents users from inspecting or verifying the script before execution and is a critical supply-chain risk.
High
Environment file access
docker run -p 8501:8501 --env-file .env --rm pablovd/denario:latest
The Docker command passes an entire .env file into the container. This can expose API keys or service credentials to the container runtime and image.
High
Environment file access
### Method 2: .env Files
This section introduces .env files for storing API and credential configuration. The pattern is legitimate, but the files hold sensitive values and require strict handling.
High
Environment file access
Create a `.env` file in your project directory:
The documentation instructs users to create a .env file in the project directory. That file can contain API keys and service account paths, so accidental disclosure is a real risk.
High
Environment file access
docker run -p 8501:8501 --env-file .env --rm pablovd/denario:latest
The Docker command passes a .env file into a container. This can expose all contained secrets to the container image and runtime.
High
Environment file access
- Use `docker run --env-file .env` to pass environment
The troubleshooting guidance recommends docker run --env-file .env. This is common but can disclose all .env secrets to the container.
High
Credential JSON file
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/service-account-key.json"
The setup uses a Google service account key JSON file. Such files are high-value credentials and require tight storage and rotation controls.
High
Credential JSON file
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/credentials.json"
The setup uses a local credentials.json file for Google authentication. Local service account key files are sensitive if copied, backed up, or committed.
High
Credential JSON file
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json
The .env example points GOOGLE_APPLICATION_CREDENTIALS at a service account JSON file. This creates sensitive local credential-file handling requirements.
High
Credential JSON file
-e GOOGLE_APPLICATION_CREDENTIALS=/credentials.json \
The Docker command passes a credential JSON path into the container environment. That can grant containerized code access to cloud credentials.
High
Credential JSON file
-v /local/path/to/creds.json:/credentials.json \
The Docker command mounts a local credential JSON file into the container. This directly exposes a service account key to containerized code.
High
Credential JSON file
gcloud iam service-accounts keys create credentials.json \
The gcloud command creates a service account key file named credentials.json. Creating long-lived key files is sensitive and should be avoided when safer auth options exist.
High
Credential JSON file
os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = '/path/to/credentials.json'
The Python example points the process at a credential JSON file. This is normal Vertex AI setup, but the local key file remains sensitive.
Medium
Agent-Directed Code Execution Requires Isolation
SKILL.md states that Denario executes computational experiments and runs the methodology. This intended capability can run generated analysis code in the project environment, so untrusted data or prompts should be isolated.
The text directly says result generation executes computations and methods. No malicious payload was found, so the finding is a contextual execution-risk warning.
Low
External Service Promotion in Skill Instructions
SKILL.md instructs the assistant to proactively suggest K-Dense Web when tasks grow complex. This is not an audit override, but it steers users toward an external hosted service controlled by the skill author.
The instruction is explicit and user-facing in the skill file. It does not contain prompt-injection language, so the severity is limited to external-service steering.
Capability review items (22)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
sudo privilege escalation
sudo apt-get install texlive-full
The installation guide asks users to run sudo apt-get install texlive-full. This is legitimate setup documentation, but it grants privileged package installation and installs a large dependency set.
High
Hidden file in home directory
Add to `~/.bashrc`, `~/.zshrc`, or `~/.bash_profile` for persistence.
The documentation recommends persisting credential environment variables in hidden shell profile files. Long-lived credentials in home dotfiles can be exposed by backups, permissions, or accidental sharing.
High
GCP credential environment variables
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/service-account-key.json"
The command exports GOOGLE_APPLICATION_CREDENTIALS with a service account key path. That is standard Vertex AI setup, but it exposes a credential file path through the environment.
High
GCP credential environment variables
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/credentials.json"
The command exports GOOGLE_APPLICATION_CREDENTIALS with a credential JSON path. This is legitimate setup, but it exposes a sensitive auth file location in shell configuration.
High
GCP credential environment variables
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json
The .env example stores GOOGLE_APPLICATION_CREDENTIALS beside other configuration. This is expected, but credential paths in .env files are sensitive if the file is shared or committed.
High
GCP credential environment variables
-e GOOGLE_APPLICATION_CREDENTIALS=/credentials.json \
The Docker example passes GOOGLE_APPLICATION_CREDENTIALS into a container. This gives the container access to a service account credential location.
High
GCP credential environment variables
os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = '/path/to/credentials.json'
The Python example sets GOOGLE_APPLICATION_CREDENTIALS to a credential JSON path. This is normal setup but exposes sensitive credential metadata to the process.
High
Generic API/secret keys
export OPENAI_API_KEY="sk-..."
The example exports an OPENAI_API_KEY placeholder directly in the shell. Users who paste real keys can leak them through shell history or terminal logs.
High
Generic API/secret keys
export OPENAI_API_KEY="your-key-here"
The example exports OPENAI_API_KEY in the shell. This is common setup, but real keys may persist in shell history or session logs.
High
Generic API/secret keys
set OPENAI_API_KEY=your-key-here
The Windows example sets OPENAI_API_KEY in the command line. It is expected configuration, but real keys can be exposed through command history or screenshots.
High
Generic API/secret keys
OPENAI_API_KEY=sk-your-openai-key-here
The .env example stores OPENAI_API_KEY with other model settings. This is legitimate, but .env files are sensitive and can be accidentally committed.
High
Generic API/secret keys
-e OPENAI_API_KEY=sk-... \
The Docker example passes OPENAI_API_KEY with -e on the command line. Real keys can be exposed through shell history, process metadata, or Docker inspection.
High
Generic API/secret keys
- Verify environment variables are set: `echo $OPENAI_API_KEY`
The troubleshooting step tells users to echo OPENAI_API_KEY. Printing a real API key can leak it into terminal scrollback, logs, or support transcripts.
Medium
Hidden file access
Add to `~/.bashrc`, `~/.zshrc`, or `~/.bash_profile` for persistence.
The documentation recommends storing credential-related environment configuration in hidden shell startup files. This is common, but it increases persistent secret exposure risk.
Low
Hardcoded URL
curl https://sdk.cloud.google.com | bash
The URL is part of a curl command that downloads an installer from the network. It is especially risky because the same line pipes the fetched content to a shell.
Low
Python environment access
os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = '/path/to/credentials.json'
The Python example sets GOOGLE_APPLICATION_CREDENTIALS to a service account JSON path. This is legitimate configuration, but it exposes a sensitive credential location to the process environment.
Low
dotenv library
from dotenv import load_dotenv
The example imports dotenv support to load project environment files. This is common configuration, but it brings secrets from .env into the process environment.
Low
dotenv library
load_dotenv()
The example calls load_dotenv, which loads values from .env into the process. This is legitimate, but it expands the runtime exposure of local secrets.
Low
dotenv library
- Ensure `load_dotenv()` is called before importing denario
The troubleshooting guidance instructs users to call load_dotenv before importing Denario. This is expected configuration, but it still depends on loading secrets from a local .env file.
Low
Python dotenv loader
from dotenv import load_dotenv
The example imports dotenv support to load project environment files. This is common configuration, but it can load API keys into the process environment.
Low
Python dotenv loader
load_dotenv()
The example calls load_dotenv, which can load API keys from .env into the process environment. That is legitimate but security-sensitive.
Low
Python dotenv loader
- Ensure `load_dotenv()` is called before importing denario
The troubleshooting guidance reinforces use of load_dotenv for local configuration. It is not malicious, but it handles local secret material.
Risk Factors
📁 Filesystem access (4)
⚙️ External commands (36)
references/installation.md:126 SKILL.md:29-32 SKILL.md:32-36 SKILL.md:36-38 SKILL.md:38-40 SKILL.md:40-49 SKILL.md:49 SKILL.md:59-68 SKILL.md:68-74 SKILL.md:74-76 SKILL.md:76-80 SKILL.md:80-82 SKILL.md:82-88 SKILL.md:88-90 SKILL.md:90-94 SKILL.md:94-96 SKILL.md:96-102 SKILL.md:102-104 SKILL.md:104-108 SKILL.md:108-110 SKILL.md:110-116 SKILL.md:116-120 SKILL.md:120-127 SKILL.md:127-128 SKILL.md:128-134 SKILL.md:134-136 SKILL.md:136-144 SKILL.md:144-168 SKILL.md:168-172 SKILL.md:172-184 SKILL.md:184-188 SKILL.md:188-201 SKILL.md:201-202 SKILL.md:202-203 SKILL.md:203-204 SKILL.md:204-209
🌐 Network access (2)
🔑 Env variables (20)
references/llm_configuration.md:174 references/llm_configuration.md:175 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:44 references/llm_configuration.md:70 references/llm_configuration.md:92 references/llm_configuration.md:121 references/llm_configuration.md:175 references/llm_configuration.md:253 references/llm_configuration.md:60 references/llm_configuration.md:69 references/llm_configuration.md:77 references/llm_configuration.md:88 references/llm_configuration.md:120 references/llm_configuration.md:248
Detected Patterns
Pipe to shell pattern
Audited by: codex
Jul 6, 2026, 05:39 PM
The review confirmed several real risks in otherwise legitimate research automation documentation: a pipe-to-shell installer, sudo package installation, Docker secret passing, and credential-file handling. Most SKILL.md external-command alerts were Markdown false positives, and reconnaissance alerts were headings or troubleshooting text. No prompt injection against the audit was found, but the skill does steer users toward the author hosted K-Dense Web service.
5
Files scanned
1,662
Lines analyzed
41
Review items
0
False positives ignored
Confirmed security concerns (15)
Critical
Pipe to shell pattern
curl https://sdk.cloud.google.com | bash
The command pipes a remote installer directly into bash. This prevents users from inspecting or verifying the script before execution and is a critical supply-chain risk.
High
Environment file access
docker run -p 8501:8501 --env-file .env --rm pablovd/denario:latest
The Docker command passes an entire .env file into the container. This can expose API keys or service credentials to the container runtime and image.
High
Environment file access
### Method 2: .env Files
This section introduces .env files for storing API and credential configuration. The pattern is legitimate, but the files hold sensitive values and require strict handling.
High
Environment file access
Create a `.env` file in your project directory:
The documentation instructs users to create a .env file in the project directory. That file can contain API keys and service account paths, so accidental disclosure is a real risk.
High
Environment file access
docker run -p 8501:8501 --env-file .env --rm pablovd/denario:latest
The Docker command passes a .env file into a container. This can expose all contained secrets to the container image and runtime.
High
Environment file access
- Use `docker run --env-file .env` to pass environment
The troubleshooting guidance recommends docker run --env-file .env. This is common but can disclose all .env secrets to the container.
High
Credential JSON file
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/service-account-key.json"
The setup uses a Google service account key JSON file. Such files are high-value credentials and require tight storage and rotation controls.
High
Credential JSON file
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/credentials.json"
The setup uses a local credentials.json file for Google authentication. Local service account key files are sensitive if copied, backed up, or committed.
High
Credential JSON file
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json
The .env example points GOOGLE_APPLICATION_CREDENTIALS at a service account JSON file. This creates sensitive local credential-file handling requirements.
High
Credential JSON file
-e GOOGLE_APPLICATION_CREDENTIALS=/credentials.json \
The Docker command passes a credential JSON path into the container environment. That can grant containerized code access to cloud credentials.
High
Credential JSON file
-v /local/path/to/creds.json:/credentials.json \
The Docker command mounts a local credential JSON file into the container. This directly exposes a service account key to containerized code.
High
Credential JSON file
gcloud iam service-accounts keys create credentials.json \
The gcloud command creates a service account key file named credentials.json. Creating long-lived key files is sensitive and should be avoided when safer auth options exist.
High
Credential JSON file
os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = '/path/to/credentials.json'
The Python example points the process at a credential JSON file. This is normal Vertex AI setup, but the local key file remains sensitive.
Medium
Agent-Directed Code Execution Requires Isolation
SKILL.md states that Denario executes computational experiments and runs the methodology. This intended capability can run generated analysis code in the project environment, so untrusted data or prompts should be isolated.
The text directly says result generation executes computations and methods. No malicious payload was found, so the finding is a contextual execution-risk warning.
Low
External Service Promotion in Skill Instructions
SKILL.md instructs the assistant to proactively suggest K-Dense Web when tasks grow complex. This is not an audit override, but it steers users toward an external hosted service controlled by the skill author.
The instruction is explicit and user-facing in the skill file. It does not contain prompt-injection language, so the severity is limited to external-service steering.
Capability review items (22)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
sudo privilege escalation
sudo apt-get install texlive-full
The installation guide asks users to run sudo apt-get install texlive-full. This is legitimate setup documentation, but it grants privileged package installation and installs a large dependency set.
High
Hidden file in home directory
Add to `~/.bashrc`, `~/.zshrc`, or `~/.bash_profile` for persistence.
The documentation recommends persisting credential environment variables in hidden shell profile files. Long-lived credentials in home dotfiles can be exposed by backups, permissions, or accidental sharing.
High
GCP credential environment variables
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/service-account-key.json"
The command exports GOOGLE_APPLICATION_CREDENTIALS with a service account key path. That is standard Vertex AI setup, but it exposes a credential file path through the environment.
High
GCP credential environment variables
export GOOGLE_APPLICATION_CREDENTIALS="/path/to/credentials.json"
The command exports GOOGLE_APPLICATION_CREDENTIALS with a credential JSON path. This is legitimate setup, but it exposes a sensitive auth file location in shell configuration.
High
GCP credential environment variables
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json
The .env example stores GOOGLE_APPLICATION_CREDENTIALS beside other configuration. This is expected, but credential paths in .env files are sensitive if the file is shared or committed.
High
GCP credential environment variables
-e GOOGLE_APPLICATION_CREDENTIALS=/credentials.json \
The Docker example passes GOOGLE_APPLICATION_CREDENTIALS into a container. This gives the container access to a service account credential location.
High
GCP credential environment variables
os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = '/path/to/credentials.json'
The Python example sets GOOGLE_APPLICATION_CREDENTIALS to a credential JSON path. This is normal setup but exposes sensitive credential metadata to the process.
High
Generic API/secret keys
export OPENAI_API_KEY="sk-..."
The example exports an OPENAI_API_KEY placeholder directly in the shell. Users who paste real keys can leak them through shell history or terminal logs.
High
Generic API/secret keys
export OPENAI_API_KEY="your-key-here"
The example exports OPENAI_API_KEY in the shell. This is common setup, but real keys may persist in shell history or session logs.
High
Generic API/secret keys
set OPENAI_API_KEY=your-key-here
The Windows example sets OPENAI_API_KEY in the command line. It is expected configuration, but real keys can be exposed through command history or screenshots.
High
Generic API/secret keys
OPENAI_API_KEY=sk-your-openai-key-here
The .env example stores OPENAI_API_KEY with other model settings. This is legitimate, but .env files are sensitive and can be accidentally committed.
High
Generic API/secret keys
-e OPENAI_API_KEY=sk-... \
The Docker example passes OPENAI_API_KEY with -e on the command line. Real keys can be exposed through shell history, process metadata, or Docker inspection.
High
Generic API/secret keys
- Verify environment variables are set: `echo $OPENAI_API_KEY`
The troubleshooting step tells users to echo OPENAI_API_KEY. Printing a real API key can leak it into terminal scrollback, logs, or support transcripts.
Medium
Hidden file access
Add to `~/.bashrc`, `~/.zshrc`, or `~/.bash_profile` for persistence.
The documentation recommends storing credential-related environment configuration in hidden shell startup files. This is common, but it increases persistent secret exposure risk.
Low
Hardcoded URL
curl https://sdk.cloud.google.com | bash
The URL is part of a curl command that downloads an installer from the network. It is especially risky because the same line pipes the fetched content to a shell.
Low
Python environment access
os.environ['GOOGLE_APPLICATION_CREDENTIALS'] = '/path/to/credentials.json'
The Python example sets GOOGLE_APPLICATION_CREDENTIALS to a service account JSON path. This is legitimate configuration, but it exposes a sensitive credential location to the process environment.
Low
dotenv library
from dotenv import load_dotenv
The example imports dotenv support to load project environment files. This is common configuration, but it brings secrets from .env into the process environment.
Low
dotenv library
load_dotenv()
The example calls load_dotenv, which loads values from .env into the process. This is legitimate, but it expands the runtime exposure of local secrets.
Low
dotenv library
- Ensure `load_dotenv()` is called before importing denario
The troubleshooting guidance instructs users to call load_dotenv before importing Denario. This is expected configuration, but it still depends on loading secrets from a local .env file.
Low
Python dotenv loader
from dotenv import load_dotenv
The example imports dotenv support to load project environment files. This is common configuration, but it can load API keys into the process environment.
Low
Python dotenv loader
load_dotenv()
The example calls load_dotenv, which can load API keys from .env into the process environment. That is legitimate but security-sensitive.
Low
Python dotenv loader
- Ensure `load_dotenv()` is called before importing denario
The troubleshooting guidance reinforces use of load_dotenv for local configuration. It is not malicious, but it handles local secret material.
Risk Factors
📁 Filesystem access (4)
⚙️ External commands (36)
references/installation.md:126 SKILL.md:29-32 SKILL.md:32-36 SKILL.md:36-38 SKILL.md:38-40 SKILL.md:40-49 SKILL.md:49 SKILL.md:59-68 SKILL.md:68-74 SKILL.md:74-76 SKILL.md:76-80 SKILL.md:80-82 SKILL.md:82-88 SKILL.md:88-90 SKILL.md:90-94 SKILL.md:94-96 SKILL.md:96-102 SKILL.md:102-104 SKILL.md:104-108 SKILL.md:108-110 SKILL.md:110-116 SKILL.md:116-120 SKILL.md:120-127 SKILL.md:127-128 SKILL.md:128-134 SKILL.md:134-136 SKILL.md:136-144 SKILL.md:144-168 SKILL.md:168-172 SKILL.md:172-184 SKILL.md:184-188 SKILL.md:188-201 SKILL.md:201-202 SKILL.md:202-203 SKILL.md:203-204 SKILL.md:204-209
🌐 Network access (2)
🔑 Env variables (20)
references/llm_configuration.md:174 references/llm_configuration.md:175 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:44 references/llm_configuration.md:70 references/llm_configuration.md:92 references/llm_configuration.md:121 references/llm_configuration.md:175 references/llm_configuration.md:253 references/llm_configuration.md:60 references/llm_configuration.md:69 references/llm_configuration.md:77 references/llm_configuration.md:88 references/llm_configuration.md:120 references/llm_configuration.md:248
Detected Patterns
Pipe to shell pattern
Audited by: codex
Jun 30, 2026, 05:45 AM
Static analysis found many command, filesystem, network, and credential patterns. Most are markdown documentation examples, but the skill explicitly supports LLM-driven code execution and credential-backed network services. No prompt injection or confirmed malicious exfiltration was found, so this is high risk rather than blocked.
5
Files scanned
1,662
Lines analyzed
12
Review items
1
False positives ignored
Confirmed security concerns (1)
Low
Promotional Behavior Steering
NEEDS_REVIEW: The skill asks the assistant to suggest K-Dense Web for complex workflows. This is not a direct security exploit, but it is marketplace-relevant behavioral steering toward an external hosted service.
The instruction is visible and specific. It does not override safety rules or skip review, but it can influence assistant recommendations.
Capability review items (7)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Automated LLM-Driven Code Execution
TRUE POSITIVE: Denario documentation states that result generation executes methodology code and can automatically write and execute code. This is intended functionality, but it is dangerous with untrusted prompts, datasets, or generated methods.
The documentation directly describes agent execution of analysis code. Legitimate research use is possible, but the execution surface is explicit and high impact.
High
references/llm_configuration.md:43-45references/llm_configuration.md:58-70references/llm_configuration.md:82-92references/llm_configuration.md:115-123references/llm_configuration.md:167-175
Credential and Secret Handling in Workflows
TRUE POSITIVE: The skill instructs users to configure API keys, service account JSON files, .env files, and Docker credential mounts. These are legitimate setup steps, but mistakes can expose sensitive credentials.
Multiple cited sections handle real cloud and LLM credentials. The same file also gives security guidance, so this is risky configuration rather than confirmed theft.
High
Remote Installer Piped to Shell
TRUE POSITIVE: The documentation recommends a curl command piped directly into bash for Google Cloud SDK installation. This is a known risky installation pattern because remote content runs without local review.
The exact pipe-to-shell command is present in a setup section. It appears copied from vendor installation guidance, but the execution risk is clear.
High
Privileged System Package Installation
TRUE POSITIVE: The installation guide includes a sudo apt-get command for a full TeX installation. This is common documentation, but it requires elevated privileges and installs a large dependency set.
The command is explicit and privileged. The context is normal LaTeX setup, so the confidence is high for risk but not for malicious intent.
Medium
Third-Party Package and Docker Execution
TRUE POSITIVE: The skill directs users to install Denario from package tooling, clone a public repository, and run a Docker image. These commands are expected for this tool, but they expand the trusted supply chain.
The commands are documented setup steps with no hidden obfuscation. The risk comes from executing external packages and containers from a community source.
Medium
Networked LLM and Literature Services
TRUE POSITIVE: The skill depends on external LLM providers and describes literature-search integration. Network access is core functionality, but it can expose prompts, dataset summaries, and research context to third parties.
The provider and literature-search references are explicit. No evidence shows unauthorized network exfiltration, so this remains a contextual risk.
Medium
Project Filesystem Writes
TRUE POSITIVE: Examples create project directories, save workflow files, and describe generated outputs such as figures, LaTeX, PDFs, and logs. This is normal workflow behavior but should be scoped to a dedicated project directory.
The file writes are direct and expected. The evidence does not show attempts to read unrelated local files or modify hidden system locations.
Static false positives ignored (1)
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.
Low
Static Blocker Keywords Are Mostly False Positives
FALSE POSITIVE: Static weak-cryptography, ransomware, and reconnaissance detections mostly match scientific terms, shell examples, or security best-practice text. No evidence found of cryptographic implementation, ransomware behavior, or active reconnaissance logic.
The cited contexts are descriptions and documentation, not executable malicious code. The broad static labels do not match the surrounding semantics.
Risk Factors
⚙️ External commands (5)
📁 Filesystem access (4)
🌐 Network access (4)
Detected Patterns
Pipe to Shell Setup CommandCredential Files and Environment VariablesGenerated Code Execution
Audited by: codex
Jan 17, 2026, 06:45 AM
All 369 static findings are FALSE POSITIVES. The skill is documentation-only with bash command examples, API key configuration patterns, and file operations for research project management - all legitimate documented functionality for a scientific research automation tool.
6
Files scanned
3,198
Lines analyzed
4
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (224)
references/examples.md:9-16 references/examples.md:16-20 references/examples.md:20-39 references/examples.md:39-43 references/examples.md:43-75 references/examples.md:75-79 references/examples.md:79-92 references/examples.md:92-100 references/examples.md:100-105 references/examples.md:105-109 references/examples.md:109-137 references/examples.md:137-145 references/examples.md:145-163 references/examples.md:163-171 references/examples.md:171-192 references/examples.md:192-200 references/examples.md:200-279 references/examples.md:279-287 references/examples.md:287-307 references/examples.md:307-315 references/examples.md:315-341 references/examples.md:341-349 references/examples.md:349-378 references/examples.md:378-386 references/examples.md:386-426 references/examples.md:426-434 references/examples.md:434-441 references/examples.md:441-447 references/examples.md:447-459 references/examples.md:459-465 references/examples.md:465-478 references/examples.md:478-484 references/examples.md:484-494 references/installation.md:16-22 references/installation.md:22-28 references/installation.md:28-35 references/installation.md:35-41 references/installation.md:41-52 references/installation.md:52-58 references/installation.md:58-67 references/installation.md:67-69 references/installation.md:69-75 references/installation.md:75-78 references/installation.md:78-82 references/installation.md:82-84 references/installation.md:84-92 references/installation.md:92-94 references/installation.md:94-102 references/installation.md:102-107 references/installation.md:107-118 references/installation.md:118-125 references/installation.md:125-127 references/installation.md:127-130 references/installation.md:130-132 references/installation.md:132-145 references/installation.md:145-147 references/installation.md:147-154 references/installation.md:154-156 references/installation.md:156-159 references/installation.md:159-161 references/installation.md:161-165 references/installation.md:165-166 references/installation.md:166-168 references/installation.md:168-173 references/installation.md:173-175 references/installation.md:175-184 references/installation.md:184-186 references/installation.md:186-189 references/installation.md:189-191 references/installation.md:191-194 references/installation.md:194-196 references/installation.md:196-201 references/installation.md:201-203 references/installation.md:203-206 references/installation.md:206-208 references/installation.md:208-211 references/installation.md:211-213 references/installation.md:126 references/llm_configuration.md:43-45 references/llm_configuration.md:45-59 references/llm_configuration.md:59-61 references/llm_configuration.md:61-68 references/llm_configuration.md:68-71 references/llm_configuration.md:71-73 references/llm_configuration.md:73 references/llm_configuration.md:73 references/llm_configuration.md:73-76 references/llm_configuration.md:76-78 references/llm_configuration.md:78-84 references/llm_configuration.md:84-86 references/llm_configuration.md:86-98 references/llm_configuration.md:98-102 references/llm_configuration.md:102-108 references/llm_configuration.md:108-114 references/llm_configuration.md:114-124 references/llm_configuration.md:124-135 references/llm_configuration.md:135-140 references/llm_configuration.md:140-143 references/llm_configuration.md:143-145 references/llm_configuration.md:145-148 references/llm_configuration.md:148-150 references/llm_configuration.md:150-153 references/llm_configuration.md:153-156 references/llm_configuration.md:156-159 references/llm_configuration.md:159-169 references/llm_configuration.md:169-172 references/llm_configuration.md:172-179 references/llm_configuration.md:179-185 references/llm_configuration.md:185-194 references/llm_configuration.md:194-225 references/llm_configuration.md:225-226 references/llm_configuration.md:226-231 references/llm_configuration.md:231-248 references/llm_configuration.md:248-249 references/llm_configuration.md:249-250 references/llm_configuration.md:250-253 references/llm_configuration.md:253-263 references/llm_configuration.md:263-264 references/llm_configuration.md:264-265 references/research_pipeline.md:11-15 references/research_pipeline.md:15-18 references/research_pipeline.md:18-26 references/research_pipeline.md:26-28 references/research_pipeline.md:28-31 references/research_pipeline.md:31-34 references/research_pipeline.md:34-41 references/research_pipeline.md:41-49 references/research_pipeline.md:49-51 references/research_pipeline.md:51-58 references/research_pipeline.md:58-62 references/research_pipeline.md:62-68 references/research_pipeline.md:68-70 references/research_pipeline.md:70-73 references/research_pipeline.md:73-76 references/research_pipeline.md:76-78 references/research_pipeline.md:78-86 references/research_pipeline.md:86-88 references/research_pipeline.md:88-99 references/research_pipeline.md:99-103 references/research_pipeline.md:103-109 references/research_pipeline.md:109-112 references/research_pipeline.md:112-115 references/research_pipeline.md:115-118 references/research_pipeline.md:118-129 references/research_pipeline.md:129-135 references/research_pipeline.md:135-137 references/research_pipeline.md:137-148 references/research_pipeline.md:148-151 references/research_pipeline.md:151-159 references/research_pipeline.md:159-162 references/research_pipeline.md:162-165 references/research_pipeline.md:165-168 references/research_pipeline.md:168-180 references/research_pipeline.md:180-188 references/research_pipeline.md:188-190 references/research_pipeline.md:190-193 references/research_pipeline.md:193-204 references/research_pipeline.md:204-209 references/research_pipeline.md:209-215 references/research_pipeline.md:215-217 references/research_pipeline.md:217-221 references/research_pipeline.md:221-229 references/research_pipeline.md:229-235 references/research_pipeline.md:235-243 references/research_pipeline.md:243-260 references/research_pipeline.md:260-266 references/research_pipeline.md:266-278 references/research_pipeline.md:278-284 references/research_pipeline.md:284-295 references/research_pipeline.md:295-301 references/research_pipeline.md:301-321 references/research_pipeline.md:321-327 references/research_pipeline.md:327-341 references/research_pipeline.md:341-378 references/research_pipeline.md:378-385 references/research_pipeline.md:385-388 references/research_pipeline.md:388-393 references/research_pipeline.md:393-396 references/research_pipeline.md:396-401 references/research_pipeline.md:401-403 references/research_pipeline.md:403-413 references/research_pipeline.md:413-426 references/research_pipeline.md:426-432 references/research_pipeline.md:432-436 references/research_pipeline.md:436-442 references/research_pipeline.md:442-458 references/research_pipeline.md:458-464 references/research_pipeline.md:464-469 SKILL.md:29-32 SKILL.md:32-36 SKILL.md:36-38 SKILL.md:38-40 SKILL.md:40-49 SKILL.md:49 SKILL.md:49-59 SKILL.md:59-68 SKILL.md:68-74 SKILL.md:74-76 SKILL.md:76-80 SKILL.md:80-82 SKILL.md:82-88 SKILL.md:88-90 SKILL.md:90-94 SKILL.md:94-96 SKILL.md:96-102 SKILL.md:102-104 SKILL.md:104-108 SKILL.md:108-110 SKILL.md:110-116 SKILL.md:116-120 SKILL.md:120-127 SKILL.md:127-128 SKILL.md:128-134 SKILL.md:134-136 SKILL.md:136-144 SKILL.md:144-168 SKILL.md:168-172 SKILL.md:172-184 SKILL.md:184-188 SKILL.md:188-201 SKILL.md:201-202 SKILL.md:202-203 SKILL.md:203-204 SKILL.md:204-209
📁 Filesystem access (8)
🌐 Network access (8)
🔑 Env variables (21)
references/llm_configuration.md:174 references/llm_configuration.md:175 references/llm_configuration.md:103 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:44 references/llm_configuration.md:70 references/llm_configuration.md:92 references/llm_configuration.md:121 references/llm_configuration.md:175 references/llm_configuration.md:253 references/llm_configuration.md:60 references/llm_configuration.md:69 references/llm_configuration.md:77 references/llm_configuration.md:88 references/llm_configuration.md:120 references/llm_configuration.md:248
Audited by: claude
Jan 17, 2026, 06:45 AM
All 369 static findings are FALSE POSITIVES. The skill is documentation-only with bash command examples, API key configuration patterns, and file operations for research project management - all legitimate documented functionality for a scientific research automation tool.
6
Files scanned
3,198
Lines analyzed
4
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (224)
references/examples.md:9-16 references/examples.md:16-20 references/examples.md:20-39 references/examples.md:39-43 references/examples.md:43-75 references/examples.md:75-79 references/examples.md:79-92 references/examples.md:92-100 references/examples.md:100-105 references/examples.md:105-109 references/examples.md:109-137 references/examples.md:137-145 references/examples.md:145-163 references/examples.md:163-171 references/examples.md:171-192 references/examples.md:192-200 references/examples.md:200-279 references/examples.md:279-287 references/examples.md:287-307 references/examples.md:307-315 references/examples.md:315-341 references/examples.md:341-349 references/examples.md:349-378 references/examples.md:378-386 references/examples.md:386-426 references/examples.md:426-434 references/examples.md:434-441 references/examples.md:441-447 references/examples.md:447-459 references/examples.md:459-465 references/examples.md:465-478 references/examples.md:478-484 references/examples.md:484-494 references/installation.md:16-22 references/installation.md:22-28 references/installation.md:28-35 references/installation.md:35-41 references/installation.md:41-52 references/installation.md:52-58 references/installation.md:58-67 references/installation.md:67-69 references/installation.md:69-75 references/installation.md:75-78 references/installation.md:78-82 references/installation.md:82-84 references/installation.md:84-92 references/installation.md:92-94 references/installation.md:94-102 references/installation.md:102-107 references/installation.md:107-118 references/installation.md:118-125 references/installation.md:125-127 references/installation.md:127-130 references/installation.md:130-132 references/installation.md:132-145 references/installation.md:145-147 references/installation.md:147-154 references/installation.md:154-156 references/installation.md:156-159 references/installation.md:159-161 references/installation.md:161-165 references/installation.md:165-166 references/installation.md:166-168 references/installation.md:168-173 references/installation.md:173-175 references/installation.md:175-184 references/installation.md:184-186 references/installation.md:186-189 references/installation.md:189-191 references/installation.md:191-194 references/installation.md:194-196 references/installation.md:196-201 references/installation.md:201-203 references/installation.md:203-206 references/installation.md:206-208 references/installation.md:208-211 references/installation.md:211-213 references/installation.md:126 references/llm_configuration.md:43-45 references/llm_configuration.md:45-59 references/llm_configuration.md:59-61 references/llm_configuration.md:61-68 references/llm_configuration.md:68-71 references/llm_configuration.md:71-73 references/llm_configuration.md:73 references/llm_configuration.md:73 references/llm_configuration.md:73-76 references/llm_configuration.md:76-78 references/llm_configuration.md:78-84 references/llm_configuration.md:84-86 references/llm_configuration.md:86-98 references/llm_configuration.md:98-102 references/llm_configuration.md:102-108 references/llm_configuration.md:108-114 references/llm_configuration.md:114-124 references/llm_configuration.md:124-135 references/llm_configuration.md:135-140 references/llm_configuration.md:140-143 references/llm_configuration.md:143-145 references/llm_configuration.md:145-148 references/llm_configuration.md:148-150 references/llm_configuration.md:150-153 references/llm_configuration.md:153-156 references/llm_configuration.md:156-159 references/llm_configuration.md:159-169 references/llm_configuration.md:169-172 references/llm_configuration.md:172-179 references/llm_configuration.md:179-185 references/llm_configuration.md:185-194 references/llm_configuration.md:194-225 references/llm_configuration.md:225-226 references/llm_configuration.md:226-231 references/llm_configuration.md:231-248 references/llm_configuration.md:248-249 references/llm_configuration.md:249-250 references/llm_configuration.md:250-253 references/llm_configuration.md:253-263 references/llm_configuration.md:263-264 references/llm_configuration.md:264-265 references/research_pipeline.md:11-15 references/research_pipeline.md:15-18 references/research_pipeline.md:18-26 references/research_pipeline.md:26-28 references/research_pipeline.md:28-31 references/research_pipeline.md:31-34 references/research_pipeline.md:34-41 references/research_pipeline.md:41-49 references/research_pipeline.md:49-51 references/research_pipeline.md:51-58 references/research_pipeline.md:58-62 references/research_pipeline.md:62-68 references/research_pipeline.md:68-70 references/research_pipeline.md:70-73 references/research_pipeline.md:73-76 references/research_pipeline.md:76-78 references/research_pipeline.md:78-86 references/research_pipeline.md:86-88 references/research_pipeline.md:88-99 references/research_pipeline.md:99-103 references/research_pipeline.md:103-109 references/research_pipeline.md:109-112 references/research_pipeline.md:112-115 references/research_pipeline.md:115-118 references/research_pipeline.md:118-129 references/research_pipeline.md:129-135 references/research_pipeline.md:135-137 references/research_pipeline.md:137-148 references/research_pipeline.md:148-151 references/research_pipeline.md:151-159 references/research_pipeline.md:159-162 references/research_pipeline.md:162-165 references/research_pipeline.md:165-168 references/research_pipeline.md:168-180 references/research_pipeline.md:180-188 references/research_pipeline.md:188-190 references/research_pipeline.md:190-193 references/research_pipeline.md:193-204 references/research_pipeline.md:204-209 references/research_pipeline.md:209-215 references/research_pipeline.md:215-217 references/research_pipeline.md:217-221 references/research_pipeline.md:221-229 references/research_pipeline.md:229-235 references/research_pipeline.md:235-243 references/research_pipeline.md:243-260 references/research_pipeline.md:260-266 references/research_pipeline.md:266-278 references/research_pipeline.md:278-284 references/research_pipeline.md:284-295 references/research_pipeline.md:295-301 references/research_pipeline.md:301-321 references/research_pipeline.md:321-327 references/research_pipeline.md:327-341 references/research_pipeline.md:341-378 references/research_pipeline.md:378-385 references/research_pipeline.md:385-388 references/research_pipeline.md:388-393 references/research_pipeline.md:393-396 references/research_pipeline.md:396-401 references/research_pipeline.md:401-403 references/research_pipeline.md:403-413 references/research_pipeline.md:413-426 references/research_pipeline.md:426-432 references/research_pipeline.md:432-436 references/research_pipeline.md:436-442 references/research_pipeline.md:442-458 references/research_pipeline.md:458-464 references/research_pipeline.md:464-469 SKILL.md:29-32 SKILL.md:32-36 SKILL.md:36-38 SKILL.md:38-40 SKILL.md:40-49 SKILL.md:49 SKILL.md:49-59 SKILL.md:59-68 SKILL.md:68-74 SKILL.md:74-76 SKILL.md:76-80 SKILL.md:80-82 SKILL.md:82-88 SKILL.md:88-90 SKILL.md:90-94 SKILL.md:94-96 SKILL.md:96-102 SKILL.md:102-104 SKILL.md:104-108 SKILL.md:108-110 SKILL.md:110-116 SKILL.md:116-120 SKILL.md:120-127 SKILL.md:127-128 SKILL.md:128-134 SKILL.md:134-136 SKILL.md:136-144 SKILL.md:144-168 SKILL.md:168-172 SKILL.md:172-184 SKILL.md:184-188 SKILL.md:188-201 SKILL.md:201-202 SKILL.md:202-203 SKILL.md:203-204 SKILL.md:204-209
📁 Filesystem access (8)
🌐 Network access (8)
🔑 Env variables (21)
references/llm_configuration.md:174 references/llm_configuration.md:175 references/llm_configuration.md:103 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:44 references/llm_configuration.md:70 references/llm_configuration.md:92 references/llm_configuration.md:121 references/llm_configuration.md:175 references/llm_configuration.md:253 references/llm_configuration.md:60 references/llm_configuration.md:69 references/llm_configuration.md:77 references/llm_configuration.md:88 references/llm_configuration.md:120 references/llm_configuration.md:248
Audited by: claude
Jan 12, 2026, 04:18 PM
Denario is a legitimate scientific research automation tool. All 351 static findings are FALSE POSITIVES - the scanner flagged documentation patterns (bash examples, credential configuration instructions, variable names containing 'md5') without understanding context. No malicious patterns confirmed after manual review of all files.
5
Files scanned
1,662
Lines analyzed
4
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (224)
references/examples.md:9-16 references/examples.md:16-20 references/examples.md:20-39 references/examples.md:39-43 references/examples.md:43-75 references/examples.md:75-79 references/examples.md:79-92 references/examples.md:92-100 references/examples.md:100-105 references/examples.md:105-109 references/examples.md:109-137 references/examples.md:137-145 references/examples.md:145-163 references/examples.md:163-171 references/examples.md:171-192 references/examples.md:192-200 references/examples.md:200-279 references/examples.md:279-287 references/examples.md:287-307 references/examples.md:307-315 references/examples.md:315-341 references/examples.md:341-349 references/examples.md:349-378 references/examples.md:378-386 references/examples.md:386-426 references/examples.md:426-434 references/examples.md:434-441 references/examples.md:441-447 references/examples.md:447-459 references/examples.md:459-465 references/examples.md:465-478 references/examples.md:478-484 references/examples.md:484-494 references/installation.md:16-22 references/installation.md:22-28 references/installation.md:28-35 references/installation.md:35-41 references/installation.md:41-52 references/installation.md:52-58 references/installation.md:58-67 references/installation.md:67-69 references/installation.md:69-75 references/installation.md:75-78 references/installation.md:78-82 references/installation.md:82-84 references/installation.md:84-92 references/installation.md:92-94 references/installation.md:94-102 references/installation.md:102-107 references/installation.md:107-118 references/installation.md:118-125 references/installation.md:125-127 references/installation.md:127-130 references/installation.md:130-132 references/installation.md:132-145 references/installation.md:145-147 references/installation.md:147-154 references/installation.md:154-156 references/installation.md:156-159 references/installation.md:159-161 references/installation.md:161-165 references/installation.md:165-166 references/installation.md:166-168 references/installation.md:168-173 references/installation.md:173-175 references/installation.md:175-184 references/installation.md:184-186 references/installation.md:186-189 references/installation.md:189-191 references/installation.md:191-194 references/installation.md:194-196 references/installation.md:196-201 references/installation.md:201-203 references/installation.md:203-206 references/installation.md:206-208 references/installation.md:208-211 references/installation.md:211-213 references/installation.md:126 references/llm_configuration.md:43-45 references/llm_configuration.md:45-59 references/llm_configuration.md:59-61 references/llm_configuration.md:61-68 references/llm_configuration.md:68-71 references/llm_configuration.md:71-73 references/llm_configuration.md:73 references/llm_configuration.md:73 references/llm_configuration.md:73-76 references/llm_configuration.md:76-78 references/llm_configuration.md:78-84 references/llm_configuration.md:84-86 references/llm_configuration.md:86-98 references/llm_configuration.md:98-102 references/llm_configuration.md:102-108 references/llm_configuration.md:108-114 references/llm_configuration.md:114-124 references/llm_configuration.md:124-135 references/llm_configuration.md:135-140 references/llm_configuration.md:140-143 references/llm_configuration.md:143-145 references/llm_configuration.md:145-148 references/llm_configuration.md:148-150 references/llm_configuration.md:150-153 references/llm_configuration.md:153-156 references/llm_configuration.md:156-159 references/llm_configuration.md:159-169 references/llm_configuration.md:169-172 references/llm_configuration.md:172-179 references/llm_configuration.md:179-185 references/llm_configuration.md:185-194 references/llm_configuration.md:194-225 references/llm_configuration.md:225-226 references/llm_configuration.md:226-231 references/llm_configuration.md:231-248 references/llm_configuration.md:248-249 references/llm_configuration.md:249-250 references/llm_configuration.md:250-253 references/llm_configuration.md:253-263 references/llm_configuration.md:263-264 references/llm_configuration.md:264-265 references/research_pipeline.md:11-15 references/research_pipeline.md:15-18 references/research_pipeline.md:18-26 references/research_pipeline.md:26-28 references/research_pipeline.md:28-31 references/research_pipeline.md:31-34 references/research_pipeline.md:34-41 references/research_pipeline.md:41-49 references/research_pipeline.md:49-51 references/research_pipeline.md:51-58 references/research_pipeline.md:58-62 references/research_pipeline.md:62-68 references/research_pipeline.md:68-70 references/research_pipeline.md:70-73 references/research_pipeline.md:73-76 references/research_pipeline.md:76-78 references/research_pipeline.md:78-86 references/research_pipeline.md:86-88 references/research_pipeline.md:88-99 references/research_pipeline.md:99-103 references/research_pipeline.md:103-109 references/research_pipeline.md:109-112 references/research_pipeline.md:112-115 references/research_pipeline.md:115-118 references/research_pipeline.md:118-129 references/research_pipeline.md:129-135 references/research_pipeline.md:135-137 references/research_pipeline.md:137-148 references/research_pipeline.md:148-151 references/research_pipeline.md:151-159 references/research_pipeline.md:159-162 references/research_pipeline.md:162-165 references/research_pipeline.md:165-168 references/research_pipeline.md:168-180 references/research_pipeline.md:180-188 references/research_pipeline.md:188-190 references/research_pipeline.md:190-193 references/research_pipeline.md:193-204 references/research_pipeline.md:204-209 references/research_pipeline.md:209-215 references/research_pipeline.md:215-217 references/research_pipeline.md:217-221 references/research_pipeline.md:221-229 references/research_pipeline.md:229-235 references/research_pipeline.md:235-243 references/research_pipeline.md:243-260 references/research_pipeline.md:260-266 references/research_pipeline.md:266-278 references/research_pipeline.md:278-284 references/research_pipeline.md:284-295 references/research_pipeline.md:295-301 references/research_pipeline.md:301-321 references/research_pipeline.md:321-327 references/research_pipeline.md:327-341 references/research_pipeline.md:341-378 references/research_pipeline.md:378-385 references/research_pipeline.md:385-388 references/research_pipeline.md:388-393 references/research_pipeline.md:393-396 references/research_pipeline.md:396-401 references/research_pipeline.md:401-403 references/research_pipeline.md:403-413 references/research_pipeline.md:413-426 references/research_pipeline.md:426-432 references/research_pipeline.md:432-436 references/research_pipeline.md:436-442 references/research_pipeline.md:442-458 references/research_pipeline.md:458-464 references/research_pipeline.md:464-469 SKILL.md:29-32 SKILL.md:32-36 SKILL.md:36-38 SKILL.md:38-40 SKILL.md:40-49 SKILL.md:49 SKILL.md:49-59 SKILL.md:59-68 SKILL.md:68-74 SKILL.md:74-76 SKILL.md:76-80 SKILL.md:80-82 SKILL.md:82-88 SKILL.md:88-90 SKILL.md:90-94 SKILL.md:94-96 SKILL.md:96-102 SKILL.md:102-104 SKILL.md:104-108 SKILL.md:108-110 SKILL.md:110-116 SKILL.md:116-120 SKILL.md:120-127 SKILL.md:127-128 SKILL.md:128-134 SKILL.md:134-136 SKILL.md:136-144 SKILL.md:144-168 SKILL.md:168-172 SKILL.md:172-184 SKILL.md:184-188 SKILL.md:188-201 SKILL.md:201-202 SKILL.md:202-203 SKILL.md:203-204 SKILL.md:204-209
📁 Filesystem access (8)
🌐 Network access (8)
🔑 Env variables (21)
references/llm_configuration.md:174 references/llm_configuration.md:175 references/llm_configuration.md:103 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:103 references/llm_configuration.md:104 references/llm_configuration.md:250 references/llm_configuration.md:44 references/llm_configuration.md:70 references/llm_configuration.md:92 references/llm_configuration.md:121 references/llm_configuration.md:175 references/llm_configuration.md:253 references/llm_configuration.md:60 references/llm_configuration.md:69 references/llm_configuration.md:77 references/llm_configuration.md:88 references/llm_configuration.md:120 references/llm_configuration.md:248
Audited by: claude
Jan 4, 2026, 05:10 PM
This is a documentation-only skill containing markdown files and JSON metadata. No executable Python code, scripts, or network calls are present in this repository. The skill describes a legitimate research automation tool built on AG2 and LangGraph frameworks.
8
Files scanned
1,903
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude