Versioned security assessment

Report ID: SA-EA7E5CA2

5/22/2026, 1:26:19 AM

datadata-api security assessment v1

Skill Security Certification Report

Audit History

Audit model: claude Historical report

Skill name: datadata-api
Version: v1
Maintainer: datadata-team
Source: github.com/datadata-team/datadata-skills/tree/master/skills/datadata-api
Coverage: 7 Files scanned · 2,698 Lines analyzed
Policy version: Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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.

This skill is a legitimate API client for the Datadata platform. All 815 static findings are false positives resulting from documentation code examples in markdown files (backtick shell commands), standard API client patterns (HTTP requests, credential storage), and heuristic entropy detection on legitimate content. The Python CLI script is well-structured, uses stdlib only, stores credentials with proper filesystem permissions (0700/0600), and connects only to the known datadata.com domain. No evidence of malicious intent, obfuscation, or data exfiltration was found.

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

7 Files scanned · 2,698 Lines analyzed

0 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.

Source

Binding unavailable
Artifact

Identity incomplete
Audit

Complete
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.

Not recorded by this audit

Network access

May connect to external services.

Observed in 16 evidence locations

Filesystem access

May read or write local files.

Observed in 13 evidence locations

Env variables

May read values from the process environment.

Observed in 19 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 28 evidence locations

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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: claude

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 (7)

Medium

references/api.md:3 references/api.md:5 references/api.md:13-14 references/cli.md:5-10 references/data-spaces.md:3 references/query-guide.md:3 SKILL.md:12-14 SKILL.md:21-25 SKILL.md:29

External command execution in documentation examples

FALSE POSITIVE: The static analyzer detected backtick patterns in reference markdown files and SKILL.md as Ruby/shell execution. These are shell command examples (curl, CLI invocations) shown in code blocks for documentation purposes. They are not executable code within the skill itself. The actual CLI execution happens through the agent running python3 scripts/datadata_query.py as a subprocess, which is the expected operation of this skill.

Medium

agents/openai.yaml:9 agents/openai.yaml:11 agents/openai.yaml:13 agents/openai.yaml:17 agents/openai.yaml:21 agents/openai.yaml:25

Ruby shell backtick patterns in agent YAML

FALSE POSITIVE: The openai.yaml agent definition includes backtick-delimited code examples demonstrating CLI usage patterns. These are instructional examples for the AI agent, not executable Ruby/shell code. The skill is designed to run datadata_query.py as a Python subprocess, which is its legitimate function.

Low

scripts/datadata_query.py:27 scripts/datadata_query.py:382 scripts/datadata_query.py:402-403 SKILL.md:57

API credential access in legitimate API client

FALSE POSITIVE: The script reads DATADATA_API_KEY from environment variables and a local config file (~/.config/datadata/config.json). This is expected behavior for a legitimate API client tool. Credentials are stored with secure filesystem permissions (0600). The access pattern is not malicious - it is the standard way CLI tools handle authentication.

Low

scripts/datadata_query.py:14 scripts/datadata_query.py:298 scripts/datadata_query.py:316 scripts/datadata_query.py:332

Network HTTP libraries in API client

FALSE POSITIVE: The script imports urllib.request and makes HTTP requests to api.datadata.com endpoints. This is expected behavior for an API client tool. The script connects only to a single known domain (datadata.com) for legitimate data query operations, with no evidence of data exfiltration or connections to unknown endpoints.

Low

scripts/datadata_query.py:31 scripts/datadata_query.py:47-48 scripts/datadata_query.py:110-112 scripts/datadata_query.py:195 scripts/datadata_query.py:566 scripts/datadata_query.py:622-627

Weak cryptographic algorithm detection on datetime import

FALSE POSITIVE: The static analyzer flagged import datetime as a weak cryptographic algorithm. The datetime module is used for timestamp calculations (API key expiry checks, device flow state expiration). No actual cryptographic operations are performed. This is a standard library import with no security implications.

Low

scripts/datadata_query.py:370 scripts/datadata_query.py:391 scripts/datadata_query.py:432 scripts/datadata_query.py:437 scripts/datadata_query.py:443 references/cli.md:20 references/cli.md:33 references/cli.md:37

Hidden file access for credential storage

FALSE POSITIVE: The script stores API keys in ~/.config/datadata/config.json with proper Unix permissions (0700 for directory, 0600 for file). This is the standard and recommended practice for CLI tools to persist credentials. The access pattern is not suspicious or malicious.

Low

scripts/datadata_query.py:129-130 references/cli.md:55 references/cli.md:63-64 references/cli.md:75 SKILL.md:25

System reconnaissance detection on whoami API call

FALSE POSITIVE: The script includes a whoami command that calls a Datadata API endpoint (/api/v1/api-keys/whoami) to verify API key validity and inspect permissions. This is not Unix system reconnaissance. The static analyzer confused the API endpoint name with the Unix whoami command.

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