Audit History

Static findings are mostly documentation examples for DrugBank access, XML parsing, package installation, local caching, and namespace URLs. I found no prompt injection, credential exfiltration, malicious command execution, or hidden behavior; user-managed credentials and DrugBank API examples should still be documented clearly.

Static findings are mostly documentation examples for DrugBank access, XML parsing, package installation, local caching, and namespace URLs. I found no prompt injection, credential exfiltration, malicious command execution, or hidden behavior; user-managed credentials and DrugBank API examples should still be documented clearly.

Static findings were largely false positives from Markdown formatting, DrugBank XML namespace strings, local cache paths, and documented API examples. No prompt injection or malicious exfiltration intent was found. The main issues are documentation patterns that could expose credentials or encourage unsafe pickle cache loading.

Static findings are mostly documentation examples for DrugBank access, XML parsing, package installation, local caching, and namespace URLs. I found no prompt injection, credential exfiltration, malicious command execution, or hidden behavior; user-managed credentials and DrugBank API examples should still be documented clearly.

Most static findings are false positives from XML namespace URLs, DrugBank identifiers, and Markdown backticks. Confirmed issues are expected but real: authenticated network access, hidden credential configuration, package installation, local cache writes, and unsafe pickle cache loading. No prompt injection evidence was found.

Most static findings are false positives from Markdown examples, DrugBank XML namespaces, and domain-specific identifier names. No prompt injection, credential exfiltration, or malicious command execution intent was found. Two documentation risks remain: plaintext credential-file guidance and an unsafe pickle cache pattern.

Static analysis reported a critical combination of command, network, filesystem, and credential indicators, but review found no malicious intent or prompt injection. Most high alerts are false positives caused by markdown code fences, XML examples, SMILES and InChI chemistry terms, and PCA field names. The real risks are legitimate DrugBank network access, credential handling guidance, and local cache examples that require user caution.

Legitimate bioinformatics research tool for accessing pharmaceutical data from DrugBank. Static findings are false positives from markdown documentation code blocks. All capabilities are consistent with stated purpose. Environment variable access is for authentication to DrugBank. Network access is to official DrugBank API endpoints. No malicious patterns detected.

Legitimate bioinformatics research tool for accessing pharmaceutical data from DrugBank. Static findings are false positives from markdown documentation code blocks. All capabilities are consistent with stated purpose. Environment variable access is for authentication to DrugBank. Network access is to official DrugBank API endpoints. No malicious patterns detected.

Legitimate scientific research tool for accessing pharmaceutical data from DrugBank. All capabilities are consistent with stated purpose. Environment variable access is for authentication to DrugBank. Network access is to official DrugBank API endpoints. No malicious patterns detected.

Legitimate scientific research tool for accessing pharmaceutical data from DrugBank. All capabilities are consistent with stated purpose. Environment variable access is for authentication to DrugBank. Network access is to official DrugBank API endpoints. No malicious patterns detected.

Legitimate scientific research tool for accessing pharmaceutical data from DrugBank. All capabilities are consistent with stated purpose. Environment variable access is for authentication to DrugBank. Network access is to official DrugBank API endpoints. No malicious patterns detected.