Versioned security assessment

Report ID: SA-0BF0370D

6/30/2026, 8:30:44 AM

generating-solana-projects security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
generating-solana-projects
Version
v2
Maintainer
MSzgy
Source
github.com/MSzgy/generating-solana-projects/tree/main/
Coverage
4 Files scanned · 1,001 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 flagged many command, filesystem, network, and script patterns, but review shows most are markdown templates, Solana configuration examples, localhost endpoints, and relative imports. No prompt injection or confirmed malicious exfiltration was found. The remaining risk is moderate because the skill uses Write and Bash-capable workflows and instructs users to run build, install, deploy, and frontend commands.

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

4 Files scanned · 1,001 Lines analyzed

5 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 3 evidence locations

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Observed in 4 evidence locations

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 4 evidence locations

Capability review items (5)
Medium
SKILL.md:13-18reference.md:45-84
User-Controlled Project Generation Requires Path Guardrails
The skill asks for a project name and then generates a complete directory tree. This is legitimate for a scaffolding skill, but implementations should normalize project names and prevent writes outside the intended workspace.
The workflow clearly depends on user-provided project names and file creation. The files do not show malicious intent, so this is a moderate implementation risk rather than a confirmed exploit.
Medium
SKILL.md:55-58README.md:84-113reference.md:479-501
External Build And Deployment Commands Need User Review
The skill provides commands for dependency installation, Anchor builds, local validators, deployment, tests, and frontend servers. These commands are expected for Solana development, but users should review generated files before running them.
The commands are explicitly documented and are normal for this domain. Risk remains because install, build, and deploy commands execute external tooling in the user environment.
Low
README.md:25-27reference.md:106-108reference.md:307-310reference.md:442-449
Template Paths Are Legitimate Solana Project References
Hidden directory and traversal findings refer to installation paths, Solana wallet configuration, and relative imports for generated clients. These are expected template references, not evidence of unauthorized file access.
The paths appear in documented templates and import statements. No instruction directs the model to read secrets or traverse arbitrary user files.
Low
reference.md:103-104reference.md:418-420examples.md:253
Network Indicators Are Expected Development Endpoints
The hardcoded URL and IP address are an Anchor registry URL and local Solana validator endpoint. They do not contain credential upload logic or suspicious remote collection behavior.
The reviewed endpoints are standard development or registry locations. No evidence found that secrets or project data are sent to an untrusted service.
Low
reference.md:385-389
Dynamic Import Alert Is A JSDoc Type Reference
The dynamic import finding points to a Next.js JSDoc type annotation in a configuration template. This does not dynamically load untrusted code at runtime.
The import syntax is inside a documentation comment used by Next.js tooling. There is no user-controlled module path or runtime import expression.

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 (2)
Low
examples.md:11-25README.md:50-70reference.md:45-85
Markdown Fences Misclassified As Shell Execution
Many static external command findings are caused by markdown code fences and project tree examples. These are documentation templates, not Ruby or shell backtick execution in runnable code.
The cited locations are fenced markdown examples and directory trees. There is no executable Ruby code or command substitution at these locations.
Low
SKILL.md:3README.md:118-120reference.md:175-179
Weak Cryptography Alerts Are Textual False Positives
Static weak cryptography findings correspond to ordinary documentation terms such as smart contracts, tests, descriptions, and frontend configuration. No weak hashing or encryption implementation was found in the reviewed locations.
The cited lines are prose or placeholders, not cryptographic operations. No evidence found for MD5, SHA-1, insecure ciphers, or custom crypto logic.

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