ClawHub

License Picker

v6.0.0

Open source license reference — SPDX identifiers, permissive vs copyleft comparison, license compatibility matrix, patent clauses, and compliance scanning tools

⭐ 0· 433·3 current·3 all-time
by@bytesagain1
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (open-source license reference) matches what is included: no required binaries, no env vars, and the script emits documentation text. Nothing requested appears unrelated to a licensing reference tool.
✓
Instruction Scope
SKILL.md explicitly says outputs are plain-text heredocs with no external API calls. The included script defines cmd_* functions that print static heredocs; no commands that read credentials, call network endpoints, or access unrelated system files were found in the provided content. (Note: the provided script listing ends with a '[truncated]' marker — review the complete file in the repository to confirm there are no additional behaviors.)
✓
Install Mechanism
There is no install spec (instruction-only behavior). A single shell script is included but no downloads, package installs, or extract operations are present.
✓
Credentials
The skill requires no environment variables or credentials and the script does not reference any env vars or secret-like names. The absence of requested secrets is proportionate to the stated purpose.
✓
Persistence & Privilege
always is false and the skill is user-invocable; it does not request elevated or persistent platform privileges.
Assessment
This skill appears safe and coherent for use as an offline licensing reference. Before installing or enabling it for autonomous agents, (1) inspect the full scripts/script.sh file in the repository (the provided listing shows '[truncated]') to confirm there are no added network calls or side effects, (2) remember this is reference material, not legal advice—consult counsel for binding interpretations, and (3) avoid granting persistent/always-on privileges unless you review future updates for behavioral changes (network calls, credential reads, or subprocess execution).

Like a lobster shell, security has layers — review code before you run it.

latestvk97fgb0wpp9e5kf1s23tpdgmq583f0wvproductivityvk97895dzq71sh1pa09dvdzba3n82rdv3

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments