Versioned security assessment

Report ID: SA-35F95435

6/30/2026, 4:49:04 PM

nodejs-backend-patterns security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
nodejs-backend-patterns
Version
v2
Maintainer
sickn33
Source
github.com/sickn33/antigravity-awesome-skills/tree/main/skills/nodejs-backend-patterns
Coverage
2 Files scanned · 1,056 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.

The static analyzer reported many high-risk patterns, but most are false positives from Markdown code fences, import paths, environment-variable examples, and reference URLs in documentation. No prompt injection or malicious intent was found, but one code example builds SQL column names from untrusted update keys and should be treated as a publish warning.

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

2 Files scanned · 1,056 Lines analyzed

2 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

    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.

Not recorded by this audit

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Observed in 13 evidence locations

External commands

May invoke commands or programs outside the Skill.

Not recorded by this audit

Risk findings

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

Confirmed security concerns (1)

RISK-001 Medium
resources/implementation-playbook.md:266-281
Unsafe Dynamic SQL Identifier Construction in Example
A repository update example derives column names from Object.keys(updates) and interpolates them into the SQL SET clause. Values are parameterized, but unvalidated column names can still create SQL injection or unauthorized-field update risk if request body keys reach this method.
The code clearly interpolates field names into SQL from an updates object. The surrounding controller assigns req.body to the update DTO, so runtime validation or a whitelist is needed before this pattern is safe.
Needs review findings (1)
REVIEW-001 Low
resources/implementation-playbook.md:75resources/implementation-playbook.md:98
Permissive Network Defaults in Example Code
The Fastify example allows any CORS origin and binds the server to 0.0.0.0. These are common development defaults, but production guidance should require explicit origins and intentional bind addresses.
The lines show permissive network behavior, but they are documentation examples and not evidence of malicious execution. The risk depends on whether users copy them into production unchanged.

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 (1)
Low
SKILL.md:31-35resources/implementation-playbook.md:25resources/implementation-playbook.md:123-124resources/implementation-playbook.md:563resources/implementation-playbook.md:997
Static Findings Mostly Come From Documentation Syntax
External command, filesystem traversal, prototype manipulation, weak crypto, and sensitive-file findings are false positives after context review. The cited areas are Markdown fences, relative imports, Object.setPrototypeOf for Error subclassing, bcrypt or JWT examples, and environment-variable configuration examples rather than executable skill behavior.
Targeted review confirmed these patterns are inside instructional Markdown or ordinary TypeScript examples. No executable script, shell command, prompt injection, or data exfiltration behavior was found.

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