security-scanning-security-sast
Scan Code for Security Vulnerabilities
Teams need repeatable source code security checks before release. This skill helps configure SAST tools, triage findings, and map fixes to secure coding patterns.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "security-scanning-security-sast" from https://skillstore.io/skills/sickn33-security-scanning-security-sast.md and its manifest at https://skillstore.io/api/skills/sickn33-security-scanning-security-sast/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "security-scanning-security-sast". Review a Python Flask service for common SAST issues.
Expected outcome:
The review highlights debug mode, weak secret key handling, unsafe file access, and missing secure headers. It recommends Bandit and Semgrep checks with prioritized fixes.
Using "security-scanning-security-sast". Add SAST scanning to a pull request workflow.
Expected outcome:
The plan runs lightweight scans on pull requests, stores reports as artifacts, and blocks only confirmed high-severity findings after triage.
Using "security-scanning-security-sast". Triage a mixed Semgrep and Bandit report.
Expected outcome:
- Confirmed injection findings are listed first.
- Likely false positives are separated with rationale.
- Each fix is mapped to an owner and severity.
Security Audit
SafeAI adjudication found no malicious behavior or prompt injection in SKILL.md. The static findings are SAST documentation examples, Semgrep rules, secure coding examples, or expected scanner command guidance rather than hidden execution, credential access, or exfiltration.
Risk Factors
⚡ Contains scripts (2)
⚙️ External commands (50)
🌐 Network access (2)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-security-scanning-security-sast/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-security-scanning-security-sast?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-security-scanning-security-sast?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-security-scanning-security-sast/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-security-scanning-security-sast.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). security-scanning-security-sast security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-security-scanning-security-sast/audits/6BibTeX citation
@techreport{sickn33-sickn33-security-scanning-security-sast-2026,
author = {sickn33},
title = {security-scanning-security-sast security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-security-scanning-security-sast/audits/6},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "security-scanning-security-sast security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-security-scanning-security-sast/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-security-scanning-security-sast:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Pull Request Security Review
Run targeted SAST checks on changed files and prioritize exploitable findings before merge.
CI Security Gate Setup
Add repeatable Bandit, Semgrep, or ESLint Security scans to a build pipeline with clear report outputs.
Legacy Code Baseline
Assess an older codebase, group findings by severity, and plan incremental remediation work.
Try These Prompts
Use the SAST skill to review this repository. Identify languages, choose suitable tools, and summarize the highest-risk vulnerability patterns.
Use the SAST skill to triage these scanner findings. Group confirmed risks, likely false positives, and fixes by severity.
Use the SAST skill to design a CI security scan for this project. Recommend tools, thresholds, artifacts, and developer feedback steps.
Use the SAST skill to draft custom Semgrep rules for our secure coding policy. Explain the target pattern, expected matches, and test cases.
Best Practices
- Run SAST early in development and again in CI before release.
- Tune rules and exclusions so developers trust the findings.
- Prioritize confirmed critical and high findings before broad cleanup work.
Avoid
- Do not upload proprietary code to external services without approval.
- Do not block releases on untriaged low-confidence findings.
- Do not rely on one scanner as the only security review method.