Versioned security assessment

Report ID: SA-0ED025F3

6/30/2026, 8:18:51 PM

react-useeffect security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
react-useeffect
Version
v3
Maintainer
softaworks
Coverage
4 Files scanned · 925 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, storage, and weak-crypto patterns, but review found markdown documentation and fenced React examples rather than executable skill behavior. No prompt injection, data exfiltration, command execution, or malicious intent was found; residual risk is low because examples discuss fetch, local storage, and auth-token handling.

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 · 925 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.

Not recorded by this audit

Network access

May connect to external services.

Not recorded by this audit

Filesystem access

May read or write local files.

Not recorded by this audit

Env variables

May read values from the process environment.

Not recorded by this audit

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.

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 (4)
Low
Static Command Findings Are Markdown False Positives
The repeated external command findings are inline code ticks and fenced TypeScript examples in documentation. They do not invoke a shell or define executable skill scripts.
The reviewed locations are markdown tables or fenced React examples. No executable Ruby, shell command, or script entry point is present in the skill files.
Low
Network References Are Educational Examples
The network findings point to prose about network requests, a generic fetch example, and official React documentation links. No skill code performs outbound requests.
The fetch call appears inside a React custom hook example, and the URLs are source references to react.dev. There is no evidence of hidden telemetry or exfiltration.
Low
Browser Storage And Auth Mentions Are Guidance
Browser storage and auth-token references appear in an anti-pattern about app initialization. The text warns that React Strict Mode can expose missing cleanup or unsafe repeated initialization.
The storage and token names are illustrative placeholder functions in markdown examples. They are not implemented functions and no sensitive data is read by the skill.
Low
Weak Cryptography Findings Are Text Matching Noise
The weak cryptography findings occur on documentation lines about React Effects, reference files, and guide structure. No cryptographic API or hashing implementation is present.
The cited lines contain prose and filenames, not MD5, SHA1, DES, or other weak cryptographic operations. No evidence of cryptographic behavior was found.

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