space-login

v1.0.2

提供模拟太空登录、身份验证、轨道认证及多星系权限管理,支持飞船绑定和实时轨道同步功能。

0· 251·0 current·0 all-time
byqinlong@pandasun
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 (simulated space login/auth) aligns with the provided Python implementation: SpaceLogin is a local simulator that manages in-memory login/logout/status. No unrelated cloud services, binaries, or credentials are requested by the code.
Instruction Scope
SKILL.md instructs typical install/use steps and CLI/Python usage that map to the code. The docs mention example environment variables (SPACE_API_KEY, SPACE_CENTER) and a config.json, but the Python code does not read those environment variables — it reads a local config file or falls back to built-in defaults. This is a documentation mismatch (misleading but not harmful).
Install Mechanism
There is no install spec and requirements.txt is empty. The README/SKILL.md suggest pip installing requirements (a no-op here). No downloads, external installers, or archive extraction are present.
Credentials
Registry metadata lists no required env vars and the package does not request secrets. However, SKILL.md shows example environment variables which are not required or consumed by the code — a documentation inconsistency. No config paths or credentials are accessed by the code.
Persistence & Privilege
Skill does not request 'always' presence and does not modify system or other skills. It runs as a local library/CLI with no autonomous or privileged side effects.
Assessment
This skill is a local simulator: the Python files implement an in-memory 'space login' experience and do not contact external services or read secrets. Notes before installing/running: 1) SKILL.md mentions environment variables (SPACE_API_KEY) that the code does not use — treat those as examples only. 2) The package has no external dependencies or installers, but you should still inspect config.json before running to ensure no sensitive values are present. 3) If you want extra assurance, run the examples in a sandbox or isolated environment; otherwise it appears safe for learning/entertainment use.

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

latestvk976249cear2asmkwk64vvgsdd829aej

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments