Versioned security assessment

Report ID: SA-37B78F02

6/28/2026, 9:30:28 PM

happyflow-generator security assessment v7

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
happyflow-generator
Version
v7
Maintainer
Chaim12345
Coverage
1 Files scanned · 1,040 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

3 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 analysis correctly identified network access, filesystem use, environment access, and subprocess execution in SKILL.md. The behavior appears aligned with an API test-generation skill, but generated scripts embed credentials and execute outbound API calls, so publication should include a clear 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

1 Files scanned · 1,040 Lines analyzed

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

Not recorded by this audit

Network access

May connect to external services.

Observed in 11 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 2 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 2 evidence locations

Capability review items (3)
Medium
Generated Script Executes Network Requests With User Credentials
The skill prepares bearer, API key, basic, and OAuth credentials, then generates a Python script that serializes AUTH_HEADERS and sends requests through a requests session. This is legitimate for API testing but can expose secrets if generated scripts, logs, or outputs are shared.
The credential handling and request generation are explicit and central to the skill. The risk is contextual because the target API and credentials are supplied by the user.
Medium
Subprocess Execution of Generated Python Script
The retry workflow writes generated Python to a temporary file and executes it with subprocess.run. This enables the intended test flow, but it also means generated code can perform network actions and should only be run in a controlled environment.
The subprocess call is direct and uses a temporary generated script. There is no shell=True evidence, so command injection is less likely than execution-risk from generated code.
Low
Temporary File Cleanup Uses Expected Local Filesystem Operations
The skill writes generated scripts to a temporary file and deletes the file afterward. This is expected for local execution, but users should avoid running it with sensitive working-directory permissions.
The filesystem behavior is direct and limited to a temporary generated script. The cleanup path is explicit, but any generated script execution still carries operational risk.

Risk findings

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

Confirmed security concerns (3)

RISK-001 Medium
Detailed Reports May Reveal API Data
The generated script stores request payloads, response headers, and the first 1000 characters of response bodies for reporting. This can expose sensitive API data in console output or saved reports.
The code explicitly captures response and request details for reporting. The sensitivity depends on the tested API and returned data.
RISK-002 Low
Static Backtick Findings Are Markdown Code Fences
The Ruby or shell backtick detections correspond to Markdown code fences around Python examples, not Ruby command execution. No shell backtick execution evidence was found in SKILL.md.
The cited lines are Markdown fence delimiters or examples. The actual executable command risk is already captured by the subprocess finding.
RISK-003 Low
Weak Cryptography Detections Are Not Cryptographic Use
The weak cryptography alerts map to descriptive text, response descriptions, and Basic auth base64 encoding. Base64 is encoding, not encryption, and no custom cryptographic implementation was found.
The only concrete encoding operation is standard Basic authentication header construction. No evidence of MD5, SHA1, DES, or similar weak cryptographic algorithms was found.

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.

Verify and export

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

Audit attestation: not_attestable