Is Cyberaudit Skill safe and trustworthy?

tashan scores Cyberaudit Skill on public evidence — tashan score 46.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Cyberaudit Skill?

In Claude Code: run `claude mcp add cyberaudit-skill -- npx -y cyberaudit-skill`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Cyberaudit Skill?

source: ArisRoman/cyberaudit-skill.

‹ The Index

Cyberaudit Skill

npm

Universal security audit skill for AI agents. Install once, audit any web or mobile app. OpenCode, Claude Code, Cursor, Kiro, Gemini — all supported.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Dev Tools & CI — see all ranked ›

Work: Security review · Audit

Who it is for: Security engineer · Finance / accounting · Legal / compliance

Install (Claude Code):

claude mcp add cyberaudit-skill -- npx -y cyberaudit-skill

solid

“3 worked examples; short of deep on per-tool docs and a stated limitation”

This grade is wrong ›

tashan score: 46.0
Instruction depth: 63.0 (solid — documents the job properly, with examples you could follow)
Adoption: 37/wk
Upkeep: 64.0
Freshness: 85.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: MIT

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 3.2.1 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Cyberaudit Skill scores 46 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-cyberaudit-skill.svg)](https://tashan.sh/capability/pkg-cyberaudit-skill.html)

npm ↗ · source ↗ · pkg:cyberaudit-skill

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?