Php Analyzer
v2.0.3Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Php Analyzer concepts, best practices, and implementation patterns.
⭐ 0· 118·0 current·0 all-time
byBytesAgain2@ckchzh
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (Php Analyzer reference) align with what is provided: local reference content and commands. The included script simply prints heredoc documentation that matches SKILL.md. No unrelated credentials, binaries, or cloud access are requested.
Instruction Scope
SKILL.md and the script are narrowly scoped to emitting plain-text reference content. Both claim no external API calls or network access, and the script does not perform network I/O or read environment variables. Minor documentation text mentions 'Required tools and access credentials' in the quickstart section (generic guidance) even though the skill requires none — this is a benign documentation inconsistency.
Install Mechanism
There is no install spec and no downloads or extract steps. The only code is a small local bash script that prints documentation. No remote installers, package pulls, or archive extraction are present.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The script does not read secrets or environment variables. This is proportional to the stated purpose.
Persistence & Privilege
The skill does not request always:true and does not attempt to persist or modify other skills or system configuration. Normal autonomous invocation is allowed by platform defaults but the skill itself does not request elevated persistence or privileges.
Assessment
This skill appears safe and coherent: it prints local reference docs and does not request credentials or network access. If you want to be extra cautious, inspect scripts/script.sh yourself (it's plain Bash) before installing. Notable minor issues: the script's VERSION variable (2.0.2) differs from the package version (2.0.3) and the help text uses a single-quoted heredoc so $VERSION won't expand there — these are documentation/sloppiness issues, not security concerns.Like a lobster shell, security has layers — review code before you run it.
latestvk9764xf8kw22wvhj31j0dydncd83gcta
License
MIT-0
Free to use, modify, and redistribute. No attribution required.