📦

Audit History

wxpusher-integration - 3 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v3 LatestNov 12, 2026, 02:40 PM No confirmed findings0No capability change
v2 Oct 18, 2026, 05:14 PM No confirmed findings0No capability change
v1 Oct 6, 2026, 06:01 PM No confirmed findings0Baseline

Nov 12, 2026, 02:40 PM

All 30 static findings are false positives: documented service endpoints, placeholders, protective configuration guidance, Markdown formatting, and readable Chinese text. No evidence found of prompt injection, credential exfiltration, concealed execution, or unauthorized messaging. Intended integrations still require protected credentials, redacted URLs, and authorization for real sends.

8
Files scanned
1,095
Lines analyzed
4
Review items
0
False positives ignored
Audited by: codex

Oct 18, 2026, 05:14 PM

All 24 static findings are false positives involving documented endpoints, placeholder configuration, Markdown syntax, installation paths, and readable Chinese text. No evidence found of prompt injection, credential exfiltration, concealed execution, or unauthorized messaging. The skill requires scoped authorization for live pushes, prefers POST, and documents credential redaction and service limitations.

8
Files scanned
998
Lines analyzed
4
Review items
0
False positives ignored
Audited by: codex

Oct 6, 2026, 06:01 PM

All 24 static findings are false positives in context: documented endpoints, placeholder configuration, installation metadata, Markdown backticks, and readable bilingual text. No evidence found of prompt injection, unauthorized credential collection, or concealed execution. The documentation requires authorized live sends, secret protection, URL redaction, and mock development tests.

8
Files scanned
930
Lines analyzed
4
Review items
0
False positives ignored
Audited by: codex