Versioned security assessment

Report ID: SA-35038C00

6/30/2026, 3:06:42 PM

fp-ts-errors security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
fp-ts-errors
Version
v2
Maintainer
sickn33
Coverage
1 Files scanned · 857 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, blocker, and reconnaissance patterns, but context shows they are Markdown code fences, TypeScript examples, and ordinary prose. The only retained risk factor is documentation-only network usage in fetch examples; no prompt injection, secret handling, executable scripts, or malicious intent was found.

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

1 item 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.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Not recorded by this audit

Capability review items (1)
Low
Instructional Fetch Examples Only
The network findings are fetch calls inside TypeScript teaching examples for TaskEither. They describe application code patterns and do not cause the skill itself to make outbound requests.
All network calls are inside Markdown code examples for wrapping async operations. No surrounding automation, installation script, or hidden endpoint was found.

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
Markdown Code Fences Misclassified as External Commands
The external command findings point to Markdown fences and inline TypeScript examples, not shell execution. No evidence found of child process APIs, shell invocation, or command strings executed by the skill.
The cited regions are fenced TypeScript snippets and a quick-reference table. Semantic review found no executable wrapper or instruction that runs those snippets automatically.
Low
Keyword-Only Blocker Matches Are False Positives
The weak cryptography and reconnaissance findings appear to be keyword matches on words such as errors, includes, find, and id in ordinary TypeScript validation examples. No evidence found of cryptographic APIs, host discovery, or system probing.
Reviewed contexts are metadata, form validation, and error handling examples. They do not contain weak hash algorithms, filesystem enumeration, or operating system reconnaissance commands.

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