Versioned security assessment

Report ID: SA-770399ED

6/28/2026, 12:16:18 PM

nextjs-optimization security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
nextjs-optimization
Version
v6
Maintainer
AI-Vibe-Prompts
Coverage
1 Files scanned · 616 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 command, network, environment, and dynamic import patterns, but review found them in Markdown guidance and Next.js examples. No prompt injection, credential exfiltration, malicious code execution, or unsafe secret handling was found in SKILL.md. The skill is low risk because it may guide an assistant to run normal project inspection and build tools.

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 · 616 Lines analyzed

0 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 6 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 1 evidence location

External commands

May invoke commands or programs outside the Skill.

Observed in 88 evidence locations

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 (5)
Low
Documentation-Only Shell Command Examples
The external command findings are Markdown examples for project inspection, build analysis, Lighthouse checks, and dependency detection. They are not hidden execution logic, and the skill file contains no runnable script wrapper that executes them automatically.
The flagged commands are inside fenced Markdown examples and match the skill purpose of auditing a local Next.js project. I found no evidence that SKILL.md contains executable automation that runs shell commands without user context.
Low
Legitimate Next.js Dynamic Import and Fetch Examples
The dynamic import and fetch findings are normal Next.js optimization examples for bundle splitting and cache behavior. The URLs are placeholders or localhost examples, and no credential or user data is sent to an external service.
The code shows instructional examples using next/dynamic, example.com, localhost, and analytics.example.com. I found no evidence of data exfiltration or obfuscated network behavior.
Low
Environment and Browser Storage References Are Benign Examples
The environment access finding is a production configuration example using process.env.NODE_ENV. The browser storage finding is a textual note that client components may use browser APIs such as localStorage.
The environment variable example reads only NODE_ENV for removeConsole behavior, and the localStorage reference is descriptive text. I found no evidence of secret file reads, credential collection, or browser storage exfiltration.
Low
Weak Cryptography Detections Are Text Matches
The weak cryptography findings appear to be scanner matches inside ordinary prose or metadata examples, such as description fields. SKILL.md does not recommend MD5, SHA-1, DES, RC4, or any weak cryptographic algorithm.
Review of the cited lines shows Next.js optimization language and SEO metadata examples, not cryptographic implementation guidance. I found no evidence of weak crypto usage in the skill.
Low
System Reconnaissance Signals Are Project Context Checks
The reconnaissance findings are tied to normal framework detection and documentation text. The skill instructs inspection of local project files to determine Next.js usage and optimization opportunities.
The relevant context is framework and performance analysis, not host or network reconnaissance. I found no evidence of commands intended to enumerate the user system beyond normal project review.

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