Versioned security assessment

Report ID: SA-33832BE5

7/1/2026, 3:49:22 AM

google-official-seo-guide security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
google-official-seo-guide
Version
v3
Maintainer
ZhanlinCui
Coverage
10 Files scanned · 8,566 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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 analysis reported many high-risk patterns, but review found they are Markdown documentation snippets and official Google example URLs, not executable skill code. No prompt injection attempt, credential exfiltration, hidden downloader, or malicious command runner was found. Residual risk is low because some examples mention local tunnels, HTTP tools, fetch, and innerHTML, so users should treat generated implementation advice as guidance to review.

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

10 Files scanned · 8,566 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.

Observed in 3 evidence locations

Network access

May connect to external services.

Observed in 5 evidence locations

Filesystem access

May read or write local files.

Not recorded by this audit

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

Capability review items (2)
Low
Static Network Findings Are Documentation Examples
The hardcoded URLs, example IP addresses, fetch calls, FTP references, and ngrok tunnel text are copied documentation examples for SEO testing and Google Search behavior. They do not run automatically and do not transmit user data from the skill.
The referenced lines are Markdown documentation or fenced examples. I found no code path that makes outbound requests during skill activation.
Low
JavaScript Examples Require Implementation Review
Some reference examples include fetch and innerHTML patterns that could be unsafe if copied into production without validation. In this skill they are inert documentation, but users should review generated implementation code before use.
The patterns are real JavaScript examples, but they are not executed by the skill. The residual risk is limited to unsafe reuse by a user or model response.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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.

Static false positives ignored (2)
Low
Command Execution Findings Are Fenced Markdown Samples
The shell and command patterns are static examples such as a local Python HTTP server, ngrok, DNS lookup commands, and structured data snippets. They are not invoked by a script or automation in the skill.
The commands appear inside Markdown code fences and explanatory documentation. No executable file, hook, installer, or runtime wrapper was found.
Low
Weak Crypto And Reconnaissance Hits Are Keyword Collisions
The weak cryptography and reconnaissance detections are caused by SEO terms, metadata examples, verification tokens, URLs, and network troubleshooting documentation. They do not implement cryptography, scanning, or system discovery logic.
Representative flagged lines are natural-language guidance or HTML examples. There is no hashing API, crypto library call, recon loop, or data collection routine.

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