dateguard

• Outcome: Review
• Latest audit: May 29, 2026 at 9:33 PM UTC
• Version:
  1.0.1

Overview

DateGuard appears to be a real local scanner, but it can persistently modify git hook behavior and handles license secrets in ways users should review first.

Install only if you are comfortable with a local shell-based scanner reading your project files and DateGuard license configuration. Prefer using the documented environment/config path instead of --license-key, avoid untrusted license tokens, and enable git hooks only after reviewing the exact lefthook.yml changes and confirming you want DateGuard to run on future commits and pushes.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access

Findings (4)

Description-Behavior Mismatch

Medium

• Confidence: 90% confidence
• Finding: The dispatcher implements git hook installation and repository configuration management, which exceeds the advertised scope of a date/time scanner. While not inherently malicious, this is a privileged side-effect that can persistently alter developer workflows and surprise users who only intended to run a scan.

Context-Inappropriate Capability

High

• Confidence: 95% confidence
• Finding: This code appends hook configuration into a repository's lefthook.yml and installs hooks, giving the skill the ability to establish persistent execution on future commits. In the context of a scanner skill, that capability is broader than necessary and increases risk because it modifies project state and can run additional code automatically later.

Context-Inappropriate Capability

High

• Confidence: 92% confidence
• Finding: The uninstall path rewrites repository hook configuration using broad text manipulation, which can remove or corrupt unrelated configuration content. Even if intended for cleanup, modifying project automation files is beyond core scanning functionality and can damage repository configuration integrity.

Missing User Warnings

Medium

• Confidence: 88% confidence
• Finding: Accepting a license key via command-line flag and exporting it to the environment can expose the credential through shell history, process listings, logs, or CI telemetry. The script does this silently, so users may unknowingly leak sensitive license material while invoking the tool.

VirusTotal

67/67 vendors flagged this skill as clean.