Versioned security assessment

Report ID: SA-28F1715B

6/30/2026, 5:09:07 PM

memory-systems security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
memory-systems
Version
v2
Maintainer
sickn33
Coverage
1 Files scanned · 229 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Low

2 confirmed security findings require attention.

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 external commands, weak cryptography, reconnaissance terms, and one URL, but context shows these are documentation false positives. The file contains Markdown guidance and conceptual examples only, with no executable command launcher, cryptographic implementation, data collection, or outbound network behavior.

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

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

Confirmed security concerns (2)

RISK-001 Low
Hardcoded URL Is Source Metadata
The URL is the source repository metadata in the skill header. It is not used for fetching, posting, or exfiltrating data.
The URL appears in static front matter as provenance metadata. I found no network call or instruction to transmit local data.
RISK-002 Low
Reconnaissance Matches Are Conceptual Retrieval Text
The reconnaissance findings are words in explanatory text or a graph query example. They do not inspect the host, enumerate files, or collect system information.
The flagged text discusses vector stores, temporal retrieval, and a parameterized graph query. No host reconnaissance command or collection workflow is present.

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 Misread as Shell Execution
The external command findings at the example section are Markdown code fences and conceptual Python snippets. They do not execute commands or invoke a shell.
The flagged backticks are Markdown fence delimiters around examples. No runtime shell API, command string, or user-controlled execution path is present.
Low
Weak Cryptography Matches Are Terminology False Positives
The high-severity weak cryptography matches are general words from memory-system documentation. No cryptographic algorithm, hashing function, encryption code, or key handling is present.
Manual review found memory architecture prose at the flagged locations. There is no crypto library usage or security-sensitive primitive.

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