Versioned security assessment

Report ID: SA-10FF6E0F

6/28/2026, 6:11:31 AM

sast-semgrep security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
sast-semgrep
Version
v6
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/appsec/sast-semgrep
Coverage
9 Files scanned · 2,126 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

1 confirmed security finding requires 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 reported many dangerous patterns, but review shows they are primarily Semgrep rule examples, vulnerable-code examples, remediation guidance, and documentation references. No malicious intent, prompt injection, credential exfiltration, or hidden runtime behavior was found. Publish with a warning that CI examples should pin Semgrep images, actions, and package versions before production use.

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

9 Files scanned · 2,126 Lines analyzed

1 item 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 4 evidence locations

Filesystem access

May read or write local files.

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

Risk findings

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

Confirmed security concerns (1)

RISK-001 Medium
assets/ci_config_examples/github-actions.yml:39assets/ci_config_examples/github-actions.yml:89assets/ci_config_examples/gitlab-ci.yml:11assets/ci_config_examples/gitlab-ci.yml:32
CI Examples Use Floating Dependencies
The CI examples use semgrep/semgrep-action@v1, pip install semgrep, and semgrep/semgrep:latest. These are normal examples, but copied pipelines may change behavior when upstream releases change.
The cited lines are real CI dependency declarations. They are not malicious, but floating versions are a recognized supply-chain maintenance risk for copied templates.

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 (5)
Low
assets/ci_config_examples/github-actions.yml:133assets/ci_config_examples/gitlab-ci.yml:40
Shell Command Substitution Is Local Result Parsing
The flagged command substitutions read Semgrep JSON output with jq and assign counts to shell variables. I did not find evidence of user-controlled command construction or exfiltration in these snippets.
The commands parse local results.json files and compare numeric counts. No untrusted input is interpolated into executable command names or arguments at these lines.
Low
assets/rule_template.yaml:96-112references/remediation_guide.md:130-160references/remediation_guide.md:200-224references/rule_library.md:219-224references/owasp_cwe_mapping.md:92-98
Dangerous APIs Appear In Educational Examples
The eval, exec, pickle, weak crypto, and command execution patterns are presented as vulnerability examples, Semgrep rules, or remediation guidance. They are not executed by the skill itself.
The surrounding headings identify these snippets as detection patterns, vulnerable examples, or rule examples. There is no active script file invoking these APIs.
Low
assets/rule_template.yaml:77-87
Secret And Environment Access Is Rule Content
The os.getenv and secret keyword detections occur in a hard-coded secret detection rule template. The text teaches users to detect or remediate secrets, not to collect environment variables.
The location is inside a Semgrep rule example named example-hardcoded-secret. It references environment variables as a remediation pattern and does not read real secrets.
Low
SKILL.md:21-23SKILL.md:280-284assets/rule_template.yaml:34-36references/owasp_cwe_mapping.md:296-300references/rule_library.md:420-425
Hardcoded URLs Are Documentation References
The hardcoded URLs point to Semgrep, OWASP, CWE, and SANS documentation. I did not find evidence that the skill makes network requests to these URLs.
The URLs appear in references and rule metadata. No fetch, curl, or HTTP execution flow is present at the cited locations.
Low
assets/semgrep_config.yaml:17assets/semgrep_config.yaml:21
Hidden Directory Patterns Are Scan Exclusions
The hidden path detections are .venv and .git entries in a Semgrep exclude list. They reduce scan scope and do not read hidden files.
The entries are under an exclude section in a configuration example. They prevent scanning those directories rather than accessing them.

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