Back to skill

Security audit

sl-trafiklab-api

Security checks across malware telemetry and agentic risk

Overview

This skill does what it says: it queries public Stockholm transit APIs and optionally stores user-selected favorite stops or routes in a local workspace file.

Install only if you are comfortable with the skill contacting SL/Trafiklab public APIs for live transit data and storing selected favorite stops/routes in `.sl/preferences.json` in your workspace. Avoid installing test requirements unless needed, or pin/exclude vulnerable pytest versions first.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (4)

Lp3

Medium
Category
MCP Least Privilege
Confidence
95% confidence
Finding
The skill invokes a Python CLI that performs network access and reads/writes workspace files, but the skill metadata declares only a binary requirement and no corresponding permissions/capabilities. This creates a transparency and consent problem: an agent or user may run the skill without realizing it can modify local state and contact external services.

Missing User Warnings

Low
Confidence
84% confidence
Finding
The skill states that favorites are stored in `.sl/preferences.json` and provides save/remove commands, but it does not clearly warn up front that using these commands will write to the user's workspace. While the writes appear expected for functionality, insufficient disclosure can lead to unintended persistence of user data or surprise state changes.

Unpinned Dependencies

Low
Category
Supply Chain
Content
pytest>=8.0.0
Confidence
94% confidence
Finding
The dependency is specified as `pytest>=8.0.0`, which is unpinned and allows future installs to resolve to different versions over time. This weakens build reproducibility and can unintentionally introduce vulnerable or breaking versions, especially in automated environments.

Known Vulnerable Dependency: pytest==8.0.0 — 2 advisory(ies): CVE-2025-71176 (pytest has vulnerable tmpdir handling); CVE-2025-71176 (pytest has vulnerable tmpdir handling)

High
Category
Supply Chain
Confidence
91% confidence
Finding
The range `pytest>=8.0.0` includes `pytest==8.0.0`, and the static finding indicates that version has a known vulnerability in tmpdir handling. Even though the requirement is not exactly pinned to 8.0.0, an install could still select a vulnerable version depending on resolution behavior or environment constraints.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.