技能 nestjs-code-audit

📦

nestjs-code-audit

Name: nestjs-code-audit
Author: amirtaherkhani

v1.0.3 內容修訂 r1 安全 📁 檔案系統存取⚙️ 外部命令🔑 環境變數

Audit NestJS Code with Evidence-Backed Findings

NestJS repositories can hide boundary flaws and runtime risks that lint results alone cannot reveal. This skill combines local evidence collection and semantic review into one prioritized report.

支援: Claude Codex Code(CC)

🥇 84 金級

Maintain this Skill? Claim it 🥇 84 金級

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

Review the Skillstore skill "nestjs-code-audit" from https://skillstore.io/skills/amirtaherkhani-nestjs-code-audit.md and its manifest at https://skillstore.io/api/skills/amirtaherkhani-nestjs-code-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/amirtaherkhani-nestjs-code-audit.md 已簽名 manifest GET /api/skills/amirtaherkhani-nestjs-code-audit/manifest 已簽名 lockfile GET /api/skills/amirtaherkhani-nestjs-code-audit/lockfile

測試它

正在使用「nestjs-code-audit」。 Review a payment module where a consumer bypasses the owning service.

預期結果:

Illustrative verdict: pass with risks for the reviewed payment scope.
Architecture finding: a consumer writes through an exported repository without enforcing the owning operation's invariant.
Minimal remedy: route the write through the owning operation.
Validation: add a boundary test proving the invariant remains enforced.

正在使用「nestjs-code-audit」。 Review a NestJS repository with missing local lint and TypeScript executables.

預期結果:

Quality gates: lint and TypeScript were not run because local executables were unavailable.
No dependencies were installed during the audit.
Semantic review remains separate from missing tool results.
Recommended next check: rerun gates after dependencies are available in an approved environment.

安全審計

安全

v1 • 2026/10/4 開啟版本化報告

Most static findings match Markdown, JavaScript strings, or ordinary repository inspection rather than threats. Optional checks execute repository-controlled tooling and pass inherited environment variables, creating execution and credential exposure risks. No evidence found of intentional exfiltration or prompt injection in the reviewed files.

已掃描檔案

839

分析行數

複核項目

已忽略的誤報

能力複核項目 (2)

這些是真實的本機能力，對此技能而言可能是預期行為，因此需要複核，但不會按已確認的惡意行為計分。

高

scripts/collect-quality-evidence.mjs:234

Synchronous spawn

const result = spawnSync(command, args, {

With --run, this executes repository-local binaries and ESLint configuration or plugins without isolation. Non-fixing flags do not prevent malicious tooling from writing files or making network requests.

中

scripts/collect-quality-evidence.mjs:237

Environment variable object

env: { ...process.env, CI: '1', FORCE_COLOR: '0', NO_COLOR: '1' },

The runner copies every parent environment variable into repository-controlled tools and ESLint plugins. Any inherited credentials become available to that executable code.

風險因素

📁 檔案系統存取 (4)

references/check-policy.md:7 scripts/collect-quality-evidence.mjs:7 scripts/collect-quality-evidence.mjs:134 scripts/collect-quality-evidence.mjs:192

⚙️ 外部命令 (50)

🔑 環境變數 (2)

references/report-template.md:47 scripts/collect-quality-evidence.mjs:237

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

https://skillstore.io/skills/amirtaherkhani-nestjs-code-audit/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/amirtaherkhani-nestjs-code-audit/security.svg)](https://skillstore.io/skills/amirtaherkhani-nestjs-code-audit?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/amirtaherkhani-nestjs-code-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/amirtaherkhani-nestjs-code-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/amirtaherkhani-nestjs-code-audit.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 引用

amirtaherkhani. (2026). nestjs-code-audit security audit report (audit version 1) [Author version 1.0.3]. Skillstore. https://skillstore.io/skills/amirtaherkhani-nestjs-code-audit/audits/1

BibTeX 引用

@techreport{amirtaherkhani-amirtaherkhani-nestjs-code-audit-2026,
  author = {amirtaherkhani},
  title = {nestjs-code-audit security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/amirtaherkhani-nestjs-code-audit/audits/1},
  note = {Author version 1.0.3}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "nestjs-code-audit security audit report (audit version 1)"
version: "1.0.3"
type: report
authors:
  - name: "amirtaherkhani"
date-released: "2026-10-04"
url: "https://skillstore.io/skills/amirtaherkhani-nestjs-code-audit/audits/1"
identifiers:
  - type: other
    value: "skillstore:amirtaherkhani-nestjs-code-audit:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 評分

評分依據證據置信度: 中

架構

100

可維護性

內容

社群

規範符合度

你可以打造什麼

Review a Feature Module

Inspect a scoped module for dependency leaks, misplaced invariants, and missing boundary tests before changing its implementation.

Assess Repository Readiness

Review architecture, runtime controls, and available quality gates to prioritize repository improvements before a release.

Inspect Authorization Boundaries

Trace authentication, resource ownership, tenant isolation, and response handling while separating proven risks from missing evidence.

試試這些提示

Start a Repository Review

Use nestjs-code-audit to review this NestJS repository without changes or command execution. Report confirmed problems and checks that were not run.

Review a Scoped Module

Audit src/payments in architecture mode without running project tools. Trace consumers and transaction ownership; report evidence, impact, remedies, and validation steps.

Review Security Controls

Audit src/auth in security mode without live service checks. Trace guards, validation, tenant ownership, and output contracts; separate confirmed risks from verification needs.

Combine Gates and Semantic Review

Perform a full NestJS audit. Inspect local tooling and configuration first; run checks only after explicit approval in isolation with credentials removed.

最佳實務

Define the review scope and preserve existing changes before collecting evidence.
Inspect local binaries and configuration before checks; use isolation and remove credentials when executing project tooling.
Require file locations, call paths, impact, remedies, and validation for every confirmed finding.

避免

Treating a heuristic match, long file, or architectural preference as a confirmed defect.
Running untrusted project tooling because non-fixing flags appear safe.
Interpreting missing checks or clean lint output as proof of application security.

常見問題

Does this skill fix code?

No. It produces an audit report; implementation requires a separately authorized phase.

Are specialist sibling skills required?

No. Bundled semantic references support standalone review; installed specialist skills can provide deeper guidance.

Which tools can use this skill?

The skill supports Claude, Codex, and Claude Code. The bundled collector requires Node.js 20 or later.

What happens when dependencies are missing?

Unavailable checks are marked not run. The audit does not install dependencies or treat missing checks as passes.

Does a scoped audit limit every compiler check?

No. Source review and lint use the requested scope, while TypeScript checks the repository configuration as a whole.

Are optional checks guaranteed to be read-only?

No. ESLint configuration, plugins, and local binaries can execute code. Inspect them and use isolation with credentials removed before running checks.