go-linter-configuration
irook661/go-linter-configuration⭐ 0🔧 0 tools
D4.9SpiderScore (registry)
Decision
Allow with Risk
Confidence
90%
go-linter-configuration has risks — usable with isolation (4.87/10, 1 critical, 1 high).
Recommended Actions
- highRun In Container1 critical vulnerabilities require isolation
- highLimit PermissionsRestrict tool access to minimum required scope
Do Not
- ✗running in production without container isolation
Risk Flags (2)
- criticalgo-linter-configuration×2[TS-E002] Remote script downloaded and executed directly
- highsandbox.not_configured[TS-C009] No sandbox
How This Was Decided
- negativew=0.5Overall quality score = 4.87/10 (grade D)
- negativew=0.81 critical security issue(s) detected
- negativew=0.51 high-severity issue(s) detected
- positivew=0.3Tool description clarity score = 5.17/10
Source: SpiderRating automated security scanUpdated: 2026-03-13Protocol: v1.1
Description Quality
Composite: 5.2 / 10
3-Layer Breakdown
Description (38%)
5.2
Security (34%)
5.0
Metadata (28%)
4.0
Description Dimensions
Intent Clarity
6.0
Permission Scope
2.5
Side Effects
2.0
Capability Disclosure
8.0
Operational Boundaries
9.0
Security Analysis
5.0
Score
1
Critical
1
High
0
Medium
0
Low
Findings Redacted
Detailed security findings are hidden during the 90-day responsible disclosure window. Maintainers have been notified.
1 HIGH2 CRITICAL
Metadata Health
Provenance (40%)
7.5
Maintenance (35%)
0.0
Popularity (25%)
3.8
Badge
Add this badge to your README:
[](https://spiderrating.com/servers/irook661/go-linter-configuration)🛡️
Protect Your Agents
Get a free API key. Every MCP tool call checked against 15,923 rated servers in real-time.
Get Free API Key →📊
Monitor All Your Servers
Dashboard for your entire MCP portfolio. Score tracking, alerts, and compliance reports.
Start Free Trial →⭐
Scan Locally (Open Source)
Run SpiderShield on your own machine. 46+ security rules, zero data leaves your system.
Star on GitHub →