スキル frame-security-scan
📦

frame-security-scan

コンテンツリビジョン r1 安全 ⚙️ 外部コマンド🌐 ネットワークアクセス🔑 環境変数

Scan and Triage Code Vulnerabilities with Frame

Security scan results need source review before teams can trust findings or apply fixes. This skill guides Frame scans, evidence-based triage, patch review, and verification.

対応: Claude Codex Code(CC)
Maintain this Skill? Claim it 📊 75 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト
Review the Skillstore skill "frame-security-scan" from https://skillstore.io/skills/lambdasec-frame-security-scan.md and its manifest at https://skillstore.io/api/skills/lambdasec-frame-security-scan/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

テストする

「frame-security-scan」を使用しています。 Illustrative request: scan a Python service locally and triage the results.

期待される結果:

  • Scan mode: local symbolic analysis; optional AI was not enabled.
  • Illustrative finding: a request value reaches a SQL execution sink without parameterization.
  • Triage: confirmed after reviewing attacker control and the source-to-sink path.
  • Next step: propose parameterized queries and review the patch before applying it.
  • A clean scan would not prove the service is secure.

「frame-security-scan」を使用しています。 Illustrative request: compare an approved patch with the earlier scan.

期待される結果:

  • Illustrative verification result: the earlier finding is no longer reported after re-scanning.
  • The reviewed diff replaces SQL string interpolation with parameter binding.
  • Project tests passed in this example; broader security coverage remains outside the scan.

セキュリティ監査

安全

All 31 static findings are false positives involving Markdown formatting, authorized tooling, a local endpoint, a repository URL, and an empty credential example. The instructions require consent for hosted AI requests, installation, and source changes. No evidence found of credential theft, unauthorized exfiltration, or prompt injection.

2
スキャンされたファイル
114
解析済み行数
0
レビュー項目
0
誤検知を無視
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: codex
このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く
セキュリティ評価

レポートリンクをコピー

https://skillstore.io/skills/lambdasec-frame-security-scan/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/lambdasec-frame-security-scan/security.svg)](https://skillstore.io/skills/lambdasec-frame-security-scan?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/lambdasec-frame-security-scan?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/lambdasec-frame-security-scan/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/lambdasec-frame-security-scan.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
学術引用 (APA · BibTeX · CFF)

APA形式の引用

lambdasec. (2026). frame-security-scan security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/lambdasec-frame-security-scan/audits/1

BibTeX形式の引用

@techreport{lambdasec-lambdasec-frame-security-scan-2026, author = {lambdasec}, title = {frame-security-scan security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/lambdasec-frame-security-scan/audits/1}, 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: "frame-security-scan security audit report (audit version 1)" version: "unspecified" type: report authors: - name: "lambdasec" date-released: "2026-10-28" url: "https://skillstore.io/skills/lambdasec-frame-security-scan/audits/1" identifiers: - type: other value: "skillstore:lambdasec-frame-security-scan:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由 証拠の信頼度: 中
41
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
91
仕様準拠

作成できるもの

Review Application Vulnerabilities

Scan application code and inspect reported flows before deciding which findings require fixes.

Triage Security Findings

Separate symbolic and model findings, inspect validation and reachability, and document evidence for each verdict.

Check Changed Code

Use changed-file scans, baselines, and SARIF output to support repository security checks.

これらのプロンプトを試す

Scan One File
Check whether Frame is installed, then scan [file] locally without AI. Summarize findings and limitations; do not install software without asking.
Triage Directory Findings
Scan [directory] without AI and save findings. Review each source-to-sink flow and explain confirmed findings, likely false positives, and unresolved questions.
Review and Verify Fixes
Triage [findings file], then propose fixes. Ask before endpoint use or source changes; show diffs, re-scan approved patches, and run project tests.
Assess Changed Code Against a Baseline
Scan files changed since [reference] using [baseline file]. Export SARIF, triage new findings, and explain verification limits without changing configuration.

ベストプラクティス

  • Start with local scanning and obtain consent before sending code to hosted endpoints.
  • Inspect attacker control, source-to-sink flow, validation, and reachability before assigning a triage verdict.
  • Review diffs, commit or back up work before approved source changes, then re-scan and run project tests.

回避

  • Treating low confidence or a clean scan as proof that code is safe.
  • Enabling hosted AI or applying source changes without explicit user agreement.
  • Suppressing findings or trusting model conclusions without reading the affected code.

よくある質問

Does this skill install Frame automatically?
No. It checks availability and shows the installation command, but requires agreement before running installation.
Which languages support symbolic scanning?
Python, JavaScript, TypeScript, Java, C, C++, and C# have symbolic frontends. Other languages require optional LLM detection.
Does source code leave my machine?
Hosted AI endpoints receive code snippets only after consent. The documented local endpoint supports keeping AI processing on your machine.
Can the skill change source files?
It can request proposed fix diffs. In-place source changes require agreement and a commit or backup; fix generation also requires an LLM endpoint.
Can I use Frame through MCP?
Yes. A connected Frame MCP server can replace CLI commands, with the same consent rules for AI, source changes, and exploit operations.
Does a clean scan guarantee security?
No. Frame can miss vulnerabilities and report false positives. Review findings, verify fixes, and run project tests.

開発者情報

作成者

lambdasec

ライセンス

Apache-2.0

Skillstore リビジョン

r1

バージョンに関する注意

作者はバージョンを宣言していません。

参照

87c9669baf85385959f9b0a344dc9dfc8d978f9c

メンテナンスの新しさ

2026/10/28

利用状況

0 ダウンロード · 0 閲覧

ファイル構成

lambdasec のその他のスキル

すべて表示
すべて表示
📦

threat-mitigation-mapping

76

脅威をセキュリティコントロールに対応付ける

作成者 wshobson

セキュリティチームは、特定された脅威を実用的なコントロールや測定可能な修復計画に結び付けることに苦労することがよくあります。このスキルは、Claude、Codex、Claude Code が緩和策のカバレッジ、ギャップ、優先順位、ロードマップを構造化するのに役立ちます。

セキュリティ&コンプライアンス 表示