Versioned security assessment

Report ID: SA-9E952417

7/23/2026, 5:37:21 AM

dast-zap security assessment v9

Skill Security Certification Report

Audit History
Scanner version 3.0.0 Audit model: codex Latest published report
Skill name
dast-zap
Version
v0.1.0
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/appsec/dast-zap
Coverage
11 Files scanned · 2,913 Lines analyzed
Policy version
skillstore-security-audit-policy-v1

Highest confirmed finding severity

High

3 confirmed security findings require attention.

Installation context

Check the current Skill page

This page summarizes report evidence only. The Skill page provides the canonical install advisory.

Open current Skill page

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

Most static detections are documentation or visible templates for authorized OWASP ZAP testing and were dismissed as false positives. Confirmed issues include privileged package installation and an API-key-in-URL example. Semantic review also found reusable fixed credentials, fail-open GitLab gates, and mutable CI dependencies; no prompt injection or malicious intent was found.

Report position

Latest published report

Latest refers to the report sequence, not to artifact currentness.

Audit attestation

Active attestation

A public attestation is available for this exact report.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

11 Files scanned · 2,913 Lines analyzed

5 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

    Commit and path bound

  2. Artifact

    Content and tree hashes bound

  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 50 evidence locations

Filesystem access

May read or write local files.

Observed in 4 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 50 evidence locations

Capability review items (2)
High
assets/github_action.yml:177
sudo privilege escalation
sudo apt-get update && sudo apt-get install -y jq
The GitHub Actions template installs jq with sudo at runtime. This is a real privileged CI step and increases supply-chain and runner-hardening risk if copied unchanged.
High
references/api_testing_guide.md:75
Generic API/secret keys
--target https://api.example.com?api_key=your-api-key \
The guide demonstrates placing an API key in a query string. Even with placeholder text, this pattern can leak credentials through logs, browser history, and proxies.

Risk findings

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

Confirmed security concerns (3)

RISK-001 High
assets/zap_context.xml:120-122assets/zap_context.xml:143-145references/authentication_guide.md:77-80
Hardcoded Sample Credentials in Reusable Templates
Reusable authentication examples contain fixed passwords such as TestPassword123!, AdminPassword123!, and SecureP@ssw0rd. Users may copy these values into real scan contexts and expose accessible test accounts.
The cited files contain literal password values in copyable context templates and documentation. The example domains reduce immediate exposure but do not remove insecure-default risk.
RISK-002 High
assets/gitlab_ci.yml:22-30assets/gitlab_ci.yml:55-65assets/gitlab_ci.yml:97-108assets/gitlab_ci.yml:159-184
Fail-Open GitLab Security Gates
The GitLab scan jobs suppress scanner failures with || true. The security gate also succeeds when the baseline report is absent.
The template explicitly suppresses three scanner exit codes and treats a missing report as a successful skip. This directly permits failed scans to bypass the gate.
RISK-003 High
assets/github_action.yml:16-19assets/github_action.yml:28-34assets/gitlab_ci.yml:9-18
Mutable CI Dependencies
The CI templates execute containers and actions referenced by mutable tags, including latest. A changed upstream tag could execute with repository permissions or CI secrets.
The cited workflows use version tags and latest container tags instead of immutable commit or image digests. CI executes those dependencies with workflow privileges.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    Hardcoded sample passwords appear in authentication templates and examples.
    Replace literal passwords with environment-variable placeholders and state that real credentials must never be committed.
  2. FIX-002
    High
    The API testing guide shows an API key in a query string.
    Remove the query-string API key pattern and recommend headers with environment-backed secret injection.
  3. FIX-003
    High
    GitLab scan failures and missing reports can pass the security gate.
    Remove || true, require report artifacts, and fail the gate when a scan or report is missing.
  4. FIX-004
    High
    CI actions and container images use mutable version tags.
    Pin GitHub Actions to commit SHAs and container images to immutable digests. Review updates through a controlled dependency process.
  5. FIX-005
    High
    The GitHub Actions template installs jq with sudo during the workflow.
    Use a pinned container image or preinstalled runner tooling to avoid runtime privileged package installation.

Expert evidence

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

Artifact subject

Marketplace commit
9e952417e76879bc9d853e1b8b2cd6d6d8d4a1c2
Content hash
6a30d5357ec7c608ba95c6ed749342df8a290da0bb1ef9ffe61e062d8fdbc877
Tree hash
3d0f38e83814c8d0fdf86e4ff9a97a9cec4f3eb7aa9fcb1f022111453796f229
Skill path
skills/agentsecops/dast-zap
Audit payload hash
d6d7e8cc79696f9eb0818acbb9dc84b2

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

JSON report Signed attestation CITATION.cff SARIF 2.1.0 Signed installation manifest Source

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

Audit attestation: active