Versioned security assessment

Report ID: SA-CFDF8DFE

6/30/2026, 5:33:15 AM

omero-integration security assessment v5

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
omero-integration
Version
v5
Maintainer
K-Dense-AI
Source
github.com/K-Dense-AI/claude-scientific-skills/tree/main/scientific-skills/omero-integration
Coverage
10 Files scanned · 5,186 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

4 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static command-execution and weak-crypto findings are false positives caused by Markdown code fences, inline code, and ordinary OMERO examples. The skill is documentation-focused, but it covers authenticated network access, credential handling, local file writes, server-side scripts, and destructive OMERO operations, so it should publish with a medium-risk warning.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

10 Files scanned · 5,186 Lines analyzed

4 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Observed in 3 evidence locations

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Observed in 3 evidence locations

Env variables

May read values from the process environment.

Observed in 1 evidence location

External commands

May invoke commands or programs outside the Skill.

Not recorded by this audit

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (4)

RISK-001 Medium
references/advanced.md:9-17references/image_processing.md:407-413references/metadata.md:161-170
Authenticated OMERO operations can modify or delete data
The documentation includes examples for deleting projects or datasets and creating or linking images and annotations. These are legitimate OMERO workflows, but misuse can remove or alter microscopy data on a server.
The cited examples call OMERO APIs that delete objects, create images, or attach files. The risk is operational misuse rather than malicious intent.
RISK-002 Medium
references/scripts.md:21-82references/scripts.md:287-305references/scripts.md:397-420
Server-side script templates execute work on OMERO servers
The skill documents OMERO.scripts that run on the OMERO server and process user-selected images or datasets. This is expected for OMERO automation, but it requires trusted scripts, parameter validation, and permission controls.
The documentation explicitly describes scripts that run server-side. The examples are normal OMERO script patterns, but the execution context increases deployment risk.
RISK-003 Low
references/connection.md:315-318
Environment variables are used for OMERO credentials
The skill recommends reading OMERO username, password, host, and port from environment variables. This is safer than hardcoding secrets, but users should still protect shell history, logs, and runtime environments.
The cited lines directly read OMERO credential-related values from os.environ. This is a legitimate pattern with residual secret-handling risk.
RISK-004 Low
references/metadata.md:209-225references/advanced.md:143-159references/scripts.md:633-635
Local file export and cleanup examples touch the filesystem
Examples create download directories, write annotation or original-file bytes, and remove temporary files. The usage is ordinary data export code, but generated paths should be validated in real workflows.
The cited examples show actual directory creation, binary writes, and file removal. They are legitimate but deserve a low filesystem risk note.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (3)
Low
SKILL.md:32references/data_access.md:9-13references/connection.md:9-22
Markdown backticks were misclassified as shell execution
Most external-command findings are false positives from Markdown code fences and inline code in documentation. I found no evidence that the skill itself executes shell commands.
The referenced lines are Markdown file references or Python code fences, not Ruby shell backtick execution. No shell command execution intent is present.
Low
references/tables.md:7references/metadata.md:29references/image_processing.md:407-413
Weak-cryptography detections are false positives
The weak-crypto scanner hits align with ordinary documentation text, image descriptions, HDF5 table references, and variable names. I found no evidence of hashing, encryption, or weak cryptographic algorithms.
The cited lines contain non-cryptographic OMERO documentation and description fields. No cryptographic API or algorithm choice appears in those contexts.
Low
references/connection.md:13-18references/connection.md:315-318references/metadata.md:209-225
Critical obfuscation heuristic is not supported by context
The dangerous-combination heuristic combines documentation examples for network connections, credentials, filesystem export, and code blocks. I found no obfuscation, hidden payload, or data exfiltration intent.
The semantic context is a scientific OMERO documentation skill. The same primitives are legitimate for authenticated microscopy data access and export.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable