Versioned security assessment

Report ID: SA-A66EB1D5

6/30/2026, 5:06:25 PM

memory-safety-patterns security assessment v2

Skill Security Certification Report

Audit History

Audit model: codex Historical report

Skill name: memory-safety-patterns
Version: v2
Maintainer: sickn33
Source: github.com/sickn33/antigravity-awesome-skills/tree/main/skills/memory-safety-patterns
Coverage: 2 Files scanned · 638 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 found command execution, filesystem, network, weak-crypto, and reconnaissance patterns, but review shows they are documentation examples inside markdown. No executable skill code, prompt injection, credential access, exfiltration behavior, or malicious intent was found. The skill is safe to publish with low residual risk from copied examples being used without local review.

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

2 Files scanned · 638 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.

Source

Binding unavailable
Artifact

Identity incomplete
Audit

Complete
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.

Observed in 1 evidence location

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 14 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 (4)

Low

External Command Patterns Are Documentation Examples

The scanner flagged thread spawning, markdown code fences, resource references, and diagnostic shell commands. These are non-executable examples in SKILL.md and the implementation playbook, not skill automation or command invocation.

The reviewed lines are markdown instructions or fenced code samples. No script file or runtime path executes these commands.

Low

resources/implementation-playbook.md:601 resources/implementation-playbook.md:602 resources/implementation-playbook.md:603

Reference Links Are Not Network Exfiltration

The hardcoded URLs point to public C++, Rust, and AddressSanitizer documentation. They are static reference links and do not send local data to an external service.

The URLs appear only as markdown links in the resources section. No fetch, curl, webhook, or request logic was found.

Low

resources/implementation-playbook.md:367

Filesystem Write Pattern Is a C Cleanup Example

The flagged file write is a C example that opens log.txt while demonstrating cleanup logic. It is not executed by the skill and does not alter files during normal skill use.

The operation is inside a fenced C code sample. There is no wrapper script or instruction that automatically runs it.

Low

Blocker Labels Are Memory Safety Terminology False Positives

Static blocker findings for weak cryptography and reconnaissance map to memory-safety text, C symbols, and resource-management examples. No cryptographic implementation, system probing routine, or network reconnaissance behavior was found.

Manual review found memory safety explanations and sample APIs at the flagged lines. The semantic context does not support malware or reconnaissance intent.

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