Audit History
pydicom - 7 audits
Version comparison
Capability and finding changes across audited versions, newest first.
| Version | Date | Result | Review items | Change vs previous |
|---|---|---|---|---|
| v7 Latest | Jul 5, 2026, 06:05 PM | 2 confirmed | 0 | No capability change |
| v6 | Jul 5, 2026, 06:05 PM | 2 confirmed | 0 | External commandsNetwork access Contains scripts |
| v5 | Jun 30, 2026, 05:29 AM | 2 confirmed | 1 | No capability change |
| v4 | Jan 17, 2026, 07:51 AM | No confirmed findings | 0 | No capability change |
| v3 | Jan 17, 2026, 07:51 AM | No confirmed findings | 0 | Contains scripts External commandsNetwork access |
| v2 | Jan 12, 2026, 04:52 PM | No confirmed findings | 0 | External commandsNetwork access Contains scripts |
| v1 | Jan 4, 2026, 04:26 PM | No confirmed findings | 0 | Baseline |
Jul 5, 2026, 06:05 PM
Most static findings are false positives caused by Markdown code fences, DICOM terms, and documentation URLs. I found no hidden shell execution, device-file access, or network reconnaissance in the cited lines. Two semantic privacy concerns remain: metadata export can expose PHI, and the skill promotes an external hosted platform for complex medical data workflows.
Confirmed security concerns (2)
Risk Factors
📁 Filesystem access (4)
⚙️ External commands (53)
🌐 Network access (6)
Jul 5, 2026, 06:05 PM
Most static findings are false positives caused by Markdown code fences, DICOM terms, and documentation URLs. I found no hidden shell execution, device-file access, or network reconnaissance in the cited lines. Two semantic privacy concerns remain: metadata export can expose PHI, and the skill promotes an external hosted platform for complex medical data workflows.
Confirmed security concerns (2)
Risk Factors
📁 Filesystem access (4)
⚙️ External commands (53)
🌐 Network access (6)
Jun 30, 2026, 05:29 AM
Static analysis reported many high-risk patterns, but review shows most are false positives from Markdown backticks, DICOM UID values, and documentation URLs. No evidence found of command execution, network exfiltration, credential harvesting, or malicious prompt injection. The meaningful risk is privacy-related: the included anonymization and metadata scripts can expose PHI if users treat them as complete clinical de-identification tools.
Confirmed security concerns (2)
Needs review findings (1)
These findings came from uncertain legacy audit verdicts, so they require review but are not counted as confirmed security issues.
Static false positives ignored (2)
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.
Risk Factors
⚡ Contains scripts (3)
📁 Filesystem access (3)
Detected Patterns
Jan 17, 2026, 07:51 AM
This is a documentation and guidance skill for the legitimate pydicom medical imaging library. All 253 static findings are false positives: the scanner misinterpreted markdown code formatting (triple backticks) as shell backtick execution, DICOM transfer syntax identifiers (JPEG, JPEG2000 compression) as weak cryptographic algorithms, and documentation reference URLs as hardcoded network endpoints. The Python scripts perform standard medical imaging operations (anonymize, convert, extract metadata) with no malicious intent, no network operations, and no credential access.
Risk Factors
⚡ Contains scripts (3)
📁 Filesystem access (1)
Jan 17, 2026, 07:51 AM
This is a documentation and guidance skill for the legitimate pydicom medical imaging library. All 253 static findings are false positives: the scanner misinterpreted markdown code formatting (triple backticks) as shell backtick execution, DICOM transfer syntax identifiers (JPEG, JPEG2000 compression) as weak cryptographic algorithms, and documentation reference URLs as hardcoded network endpoints. The Python scripts perform standard medical imaging operations (anonymize, convert, extract metadata) with no malicious intent, no network operations, and no credential access.
Risk Factors
⚡ Contains scripts (3)
📁 Filesystem access (1)
Jan 12, 2026, 04:52 PM
This is a documentation and guidance skill for the legitimate pydicom medical imaging library. All 245 static findings are false positives: the scanner misinterpreted markdown code formatting as shell commands, DICOM compression transfer syntaxes (JPEG, JPEG2000) as cryptographic algorithms, and documentation URLs as hardcoded network endpoints. The scripts perform standard medical imaging operations with no malicious intent. Risk is limited to standard PHI handling concerns in healthcare contexts.
Risk Factors
⚙️ External commands (137)
🌐 Network access (47)
📁 Filesystem access (4)
Jan 4, 2026, 04:26 PM
Legitimate medical imaging skill with 3 Python scripts for DICOM processing. Scripts perform local file operations only - read user-specified DICOM files and write output files. No network calls, no credential access, no command execution. Standard filesystem access for file I/O is expected for this purpose.