Security audit
Security checks for vulnerabilities and agentic risk
This garden-planning skill is purpose-aligned and transparent about its local garden file and Open-Meteo weather lookup.
Before installing, understand that weather and ZIP-based frost checks contact Open-Meteo with your location or coordinates, and that plant and watering records are saved locally under the disclosed garden data directory unless you override it.
This variant of the mismatch finding includes undeclared external weather/geocoding API access, which creates a real security concern when combined with absent permissions. Hidden or insufficiently disclosed network behavior can expose location-related data and violate user expectations about what a gardening skill transmits externally.
This variant of the mismatch finding includes undeclared external weather/geocoding API access, which creates a real security concern when combined with absent permissions. Hidden or insufficiently disclosed network behavior can expose location-related data and violate user expectations about what a gardening skill transmits externally.
This variant of the mismatch finding includes undeclared external weather/geocoding API access, which creates a real security concern when combined with absent permissions. Hidden or insufficiently disclosed network behavior can expose location-related data and violate user expectations about what a gardening skill transmits externally.
This variant of the mismatch finding includes undeclared external weather/geocoding API access, which creates a real security concern when combined with absent permissions. Hidden or insufficiently disclosed network behavior can expose location-related data and violate user expectations about what a gardening skill transmits externally.
The skill advertises scripts that write local state to garden.json and perform network access for weather lookup, but it declares no permissions or allowed-tools scope. Missing capability scoping weakens least-privilege controls and can let a seemingly harmless gardening skill gain broader file-write or network behavior than users and policy engines expect.
The trigger terms are broad enough to activate on ordinary gardening conversation, increasing the chance the skill runs unintentionally. Over-broad invocation expands exposure to its file-write and network behaviors, causing unnecessary data access or external requests in contexts where the user did not intend to use this skill.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import urllib.error
from datetime import datetime, date, timedelta
FORECAST_URL = "https://api.open-meteo.com/v1/forecast"
GEOCODE_URL = "https://geocoding-api.open-meteo.com/v1/search"
FROST_THRESHOLD_C = 0.0 # 32°F
The geocoding request hard-codes language: "en", which imposes a specific language/locale in returned place names. This is a natural-language policy concern because the skill does not offer user opt-in or explain why English-only output is required.