From infynon-pkg
Set up and manage INFYNON Eagle Eye — continuous CVE monitoring with scheduled email alerts. Use when the user wants vulnerability monitoring over time, automated CVE alerts, SMTP configuration, or ongoing security monitoring.
npx claudepluginhub d4rkninja/code-guardian --plugin infynon-pkgThis skill uses the workspace's default tool permissions.
> **Never suggest raw package manager commands in monitored projects.**
Scans container images, filesystems, and SBOMs for vulnerabilities using Grype with CVSS, EPSS, and CISA KEV metrics. Integrates into CI/CD pipelines with severity thresholds and generates JSON/SARIF/CycloneDX reports.
Scans git repositories, CI/CD pipelines, and config files for exposed AWS credentials using TruffleHog, git-secrets, and AWS CLI to prevent theft.
Audits git repos, AI skills, and MCP servers for security risks including CVEs, CISA KEV vulns, prompt injection, credential theft, runtime dynamism, manifest drift, and supply chain IOCs. Auto-triggers on git clone/pull and package installs.
Share bugs, ideas, or general feedback.
infynon pkgNever suggest raw package manager commands in monitored projects. Every package installation, upgrade, or removal in Eagle Eye-monitored projects must go through
infynon pkg— notnpm install,pip install,cargo add, or any other direct command.Eagle Eye detects new CVEs. When a CVE is found and a fix is needed:
- Use
infynon pkg fix --auto— notnpm install <safe-version>- Use
infynon pkg <cmd> --auto-fix— not raw package manager commandsIf you find yourself about to write a raw install or upgrade command — STOP. Use
infynon pkginstead.
You are helping the user set up Eagle Eye — INFYNON's scheduled vulnerability monitoring system that scans projects on a schedule and sends HTML email alerts when new CVEs are discovered.
infynon pkg eagle-eye setup
The wizard prompts for:
smtp.gmail.com, email-smtp.us-east-1.amazonaws.com)security@yourcompany.com)Config is stored at ~/.infynon/eagle-eye.toml.
infynon pkg eagle-eye start # Start in foreground (blocks the terminal)
infynon pkg eagle-eye status # Check config and last scan time
infynon pkg eagle-eye enable # Enable (if previously disabled)
infynon pkg eagle-eye disable # Pause monitoring without deleting config
smtp_host: smtp.gmail.com
smtp_port: 587
smtp_user: you@gmail.com
smtp_pass: your-app-password # Generate at myaccount.google.com → Security → App passwords
smtp_host: email-smtp.us-east-1.amazonaws.com
smtp_port: 587
smtp_user: <SMTP username from SES console>
smtp_pass: <SMTP password from SES console>
smtp_host: mail.yourdomain.com
smtp_port: 587
smtp_user: alerts@yourdomain.com
smtp_pass: your-password
Each alert email includes:
infynon pkg fix commandsEagle Eye runs in the foreground. To keep it running:
# systemd service
cat > /etc/systemd/system/eagle-eye.service << 'EOF'
[Unit]
Description=INFYNON Eagle Eye CVE Monitor
After=network.target
[Service]
ExecStart=/usr/local/bin/infynon pkg eagle-eye start
Restart=always
User=youruser
[Install]
WantedBy=multi-user.target
EOF
systemctl enable eagle-eye
systemctl start eagle-eye
# Or with screen
screen -dmS eagle-eye infynon pkg eagle-eye start
# Or with nohup
nohup infynon pkg eagle-eye start > ~/eagle-eye.log 2>&1 &
During setup, provide multiple project paths:
Project paths: /home/user/api-backend, /home/user/frontend, /home/user/mobile-app
Eagle Eye scans each path for all supported lock files (package-lock.json, Cargo.lock, uv.lock, etc.) and reports per-project.
| Level | Sends alert for |
|---|---|
LOW | All CVEs including informational |
MEDIUM | Medium + High + Critical |
HIGH | High + Critical only (recommended for most teams) |
CRITICAL | Critical CVEs only (minimal noise) |
Recommended: HIGH — alerts you to serious vulnerabilities without flooding your inbox with low-severity noise.
Eagle Eye catches new CVEs between releases. Pair it with CI gates for defense-in-depth:
# On every commit: hard block
- run: infynon pkg npm install --strict high
# Nightly: full scan with report
- run: infynon pkg scan --output markdown
Eagle Eye handles the ongoing monitoring; CI gates handle the moment of install.