Audit History
starknet-identity - 3 audits
Version comparison
Capability and finding changes across audited versions, newest first.
Aug 7, 2026, 09:01 AM
The static findings are predominantly false positives caused by Markdown code fences, documentation URLs, examples, and standard configuration syntax. The private-key signer example is a confirmed high-impact secret-handling risk, so publication requires author remediation.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (35)
🌐 Network access (7)
📁 Filesystem access (2)
🔑 Env variables (2)
Jul 21, 2026, 04:35 AM
Static detections are false positives caused by Markdown code formatting, documentation links, and illustrative configuration. The skill contains expected on-chain transaction examples, but it does not provide adequate safeguards before signed writes are broadcast.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (35)
🌐 Network access (7)
📁 Filesystem access (2)
🔑 Env variables (2)
Jul 10, 2026, 12:21 AM
Most static alerts are Markdown formatting, reference links, example URLs, or standard A2A discovery paths. I confirmed one high-risk issue: the account setup example uses a privateKey signer without explicit key-management guidance. No evidence found of prompt injection, credential exfiltration, hidden downloads, or malicious system reconnaissance.