Eventsight

jonny-jhnson/EventSightMIT36🔧 16 tools

F2.0SpiderScore (registry)
⚠ Hard constraint applied: critical vulnerability
Decision
Not Recommended
Confidence
90%

Eventsight is not recommended — low score (2.0/10) with 2 critical issues.

Recommended Actions

  • high
    Run In Container
    2 critical vulnerabilities require isolation
  • high
    Limit Permissions
    Restrict tool access to minimum required scope

Do Not

  • running in production without container isolation
  • using for security-sensitive tasks
Risk Flags (3)
  • critical
    metadata_secret_leak×2
    Hardcoded secret or API key found in source code
  • high
    token_leakage×14
    Secret or token may be leaked through error messages, logs, or return values
  • high
    unsafe_path_resolution×2
    File operation on user-controlled path without validation or sandboxing
How This Was Decided
  • negativew=0.5Overall quality score = 2.0/10 (grade F)
  • negativew=0.82 critical security issue(s) detected
  • negativew=0.516 high-severity issue(s) detected
  • negativew=0.3Tool description clarity score = 2.7/10
Source: SpiderRating automated security scanUpdated: 2026-03-22Protocol: v1.1

Description Quality

Composite: 2.7 / 10

3-Layer Breakdown

Description (38%)
2.7
Security (34%)
7.5
Metadata (28%)
5.1

Description Dimensions

Intent Clarity
3.2
Permission Scope
0.0
Side Effects
2.0
Capability Disclosure
5.6
Operational Boundaries
3.3

Security Analysis

7.5
Score
2
Critical
16
High
0
Medium
11
Low

Findings Redacted

Detailed security findings are hidden during the 90-day responsible disclosure window. Maintainers have been notified.

16 HIGH2 CRITICAL

Metadata Health

Provenance (40%)
8.0
Maintenance (35%)
2.0
Popularity (25%)
4.7

Badge

Add this badge to your README:

[![SpiderRating](https://spiderrating.com/badge/jonny-jhnson__EventSight.svg)](https://spiderrating.com/servers/jonny-jhnson/EventSight)