tracking-discover — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited tracking-discover (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill for analysis-only work and fresh workflow bootstrap.
In this repository, use the repo-root wrapper:
./event-tracking analyze <url> --output-root <output-root>analyze launches a real Chromium via Playwright to fetch the target site over HTTP. Run it in an environment that permits outbound network and local browser execution; environments that restrict either tend to cause Playwright to hang or fail silently rather than return a clean error. Before run-new-setup or analyze, if the tool needs a telemetry consent answer and no prior choice is already recorded, stop and follow ../../references/telemetry-consent.md. Do not choose on the user's behalf, and do not continue until they answer.
Partial mode:
./event-tracking analyze <url> --output-root <output-root> --urls https://example.com/page-a,https://example.com/page-bProduce and share:
<artifact-dir>/site-analysis.json<artifact-dir>/workflow-state.jsonReport:
dataLayer eventsUnless the user explicitly asks for the next phase, stop after analysis. If telemetry consent is still unanswered, stop before analysis starts and wait for the user's explicit choice.
If the user wants to continue, the default next command is:
./event-tracking status <artifact-dir>~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.