Versioned security assessment

Report ID: SA-62A629A3

7/1/2026, 1:04:53 AM

nodejs-backend-patterns security assessment v5

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
nodejs-backend-patterns
Version
v5
Maintainer
wshobson
Coverage
1 Files scanned · 1,021 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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 high-risk patterns, but review found the skill is a Markdown guidance file with TypeScript examples rather than runnable scripts. Most detections are false positives from code fences, relative imports, environment-variable configuration, and resource links. One backend example teaches dynamic SQL identifier construction from object keys, so the skill should publish with a security 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

1 Files scanned · 1,021 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.

Observed in 1 evidence location

Network access

May connect to external services.

Observed in 5 evidence locations

Filesystem access

May read or write local files.

Observed in 11 evidence locations

Env variables

May read values from the process environment.

Observed in 24 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 47 evidence locations

Capability review items (2)
Medium
Unsafe Dynamic SQL Update Example
The repository update example builds a SQL SET clause from Object.keys(updates) and interpolates each field name into the query. Values are parameterized, but column names are not allowlisted, so copying this pattern can create SQL injection risk if request bodies are mapped into updates.
The vulnerable pattern is visible in the example: object keys become SQL identifiers before query execution. It is documentation rather than active code, so the risk is unsafe guidance rather than direct exploitation of this skill.
Low
Broad Network Binding Example Requires Deployment Review
The Fastify example binds to 0.0.0.0. This is common in containers but exposes the service on all interfaces if copied into a reachable host without firewall or ingress controls.
The pattern is explicit and can be risky in some deployments. It is also legitimate for containerized services, so severity is low in this documentation context.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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
Static Findings Are Mostly Documentation False Positives
The external command, filesystem traversal, prototype manipulation, network URL, credential access, and weak-crypto detections occur inside Markdown examples or ordinary documentation. Examples include TypeScript code fences, relative imports, Object.setPrototypeOf for Error subclassing, environment-variable configuration, and links to public framework documentation.
The reviewed locations are clearly Markdown documentation and TypeScript examples. I found no executable installer, script file, hidden network call, prompt injection text, or instruction to exfiltrate secrets.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable