Versioned security assessment

Report ID: SA-BFF76848

7/8/2026, 9:58:08 AM

auth-implementation-patterns security assessment v4

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
auth-implementation-patterns
Version
v4
Maintainer
sickn33
Source
github.com/sickn33/antigravity-awesome-skills/tree/main/skills/auth-implementation-patterns
Coverage
2 Files scanned · 667 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

1 confirmed security finding requires 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.

Most 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

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

    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.

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
resources/implementation-playbook.md:329
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
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.

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