agent-timezone-lock@1.2.1
CAUTIONPublisher claims: "Stops an OpenClaw agent from reporting the wrong time. Prevents the UTC-as-local mistake. Use when (1) the user reports a wrong time, (2) asks what time it is, (3) says 'set my timezone', or (4) agent output shows a time clearly off. Does NOT trigger on generic mentions of UTC, timezone, or heartbeats — only when time accuracy is explicitly at issue." Observed in sandbox: static analysis only — behavior not yet observed.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-30 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Instructs the agent to modify its persistent memory or instruction files; Instructs the agent to modify its persistent memory or instruction files; Instructs the agent to modify its persistent memory or instruction files. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
What would make this Verified
11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim ferrentinomj-dev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.