Versioned security assessment

Report ID: SA-24B2FE42

7/9/2026, 3:29:01 PM

auth-wechat-miniprogram security assessment v1

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
auth-wechat-miniprogram
Version
v1
Maintainer
tencentcloudbase
Coverage
1 Files scanned · 536 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

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 detections are false positives caused by Markdown inline code, fenced JavaScript examples, reference URLs, and sibling skill paths. The review found two medium-risk content issues: an authorization example that relies on client-supplied owner data and examples that log sensitive identifiers.

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

Observed in 4 evidence locations

Filesystem access

May read or write local files.

Observed in 2 evidence locations

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 50 evidence locations

Risk findings

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

Confirmed security concerns (2)

RISK-001 Medium
Client-Supplied Authorization Boundary
The authorization example compares verified OPENID to event.resourceOwnerId. In a Mini Program cloud function, event data is client-supplied, so this can teach unsafe ownership checks if used alone.
The code example directly uses event.resourceOwnerId as the authorization boundary. Legitimate use is possible, but auth guidance should derive ownership from server-side data.
RISK-002 Medium
Sensitive Identifier Logging in Examples
Several examples log OPENID, UNIONID, or auth result objects. These identifiers are sensitive and should be masked or limited to local debugging guidance.
The examples explicitly log user identifiers and auth user objects. The intent appears instructional, but the pattern can expose private identifiers in production logs.

Remediation

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

  1. FIX-001
    Medium
    Authorization example uses client-supplied owner data.
    Revise the example to fetch the resource owner from server-side storage and compare that value to verified OPENID.
  2. FIX-002
    Medium
    Examples log OPENID, UNIONID, and auth user objects.
    Mask identifiers in examples and state that full identity logs should be limited to local debugging.

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

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

Audit attestation: not_attestable