Versioned security assessment

Report ID: SA-86D877F2

7/23/2026, 8:32:52 PM

auth-implementation-patterns security assessment v5

Skill Security Certification Report

Audit History
Scanner version 3.0.0 Audit model: codex Latest published report
Skill name
auth-implementation-patterns
Version
v5
Maintainer
sickn33
Coverage
2 Files scanned · 667 Lines analyzed
Policy version
skillstore-security-audit-policy-v1

Highest confirmed finding severity

High

1 confirmed security finding requires attention.

Installation context

Check the current Skill page

This page summarizes report evidence only. The Skill page provides the canonical install advisory.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

The static hits are false positives from Markdown examples that show environment-based configuration and inline code paths. One semantic issue remains: the OAuth callback example redirects with an access token in a query string, which can leak through history, logs, and referrers.

Report position

Latest published report

Latest refers to the report sequence, not to artifact currentness.

Audit attestation

Active attestation

A public attestation is available for this exact report.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

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

    Commit and path bound

  2. Artifact

    Content and tree hashes bound

  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.

Observed in 11 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 3 evidence locations

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (1)

RISK-001 High
Access Token Exposed in OAuth Redirect URL
The OAuth callback example redirects to the frontend with token=${tokens.accessToken} in the query string. Access tokens in URLs can leak through browser history, logs, analytics, and referrer headers.
The code sample directly places the generated access token in the redirect URL. This is a well-known token exposure risk in OAuth callback handling.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    OAuth callback example places an access token in a redirect URL.
    Use an authorization code exchange or set a secure HttpOnly SameSite cookie. Keep tokens out of query strings, logs, and referrer headers.
  2. FIX-002
    Low
    Secret examples rely on non-null environment variable assertions.
    Add startup validation for required secrets and document secret manager usage. Fail closed when JWT, session, Redis, or OAuth settings are missing.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
86d877f219e2131f05dd5b37c5e329c71c7b8ec4
Content hash
ac7abc9e3e8928323153ecc00619359cbdb56272831ed399c4b552b193132c96
Tree hash
eb12e2344fe28837ec29925cde605cc381a0c68204ba63f66c608849d907a17c
Skill path
skills/sickn33/auth-implementation-patterns
Audit payload hash
b1a135d96e08ce6f3c1ac065aa3cea60

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.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: active