gitserver-http

gitserver-http is an HTTP-oriented service for accessing a Git repository over HTTP. It typically exposes Git transport operations (e.g., smart HTTP endpoints) so clients can clone/fetch/pull without running a separate SSH git daemon.

Evaluated Apr 04, 2026 (25d ago)
Homepage ↗ Repo ↗ Infrastructure git version-control http self-hosted reverse-proxy
⚙ Agent Friendliness
31
/ 100
Can an agent use this?
🔒 Security
45
/ 100
Is it safe for agents?
⚡ Reliability
32
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
0
Documentation
20
Error Messages
0
Auth Simplicity
45
Rate Limits
20

🔒 Security

TLS Enforcement
70
Auth Strength
35
Scope Granularity
20
Dep. Hygiene
40
Secret Handling
60

Security depends heavily on deployment configuration (TLS termination, access control, auth at proxy, and repository permissions). Without explicit evidence of fine-grained auth and documented security controls, treat it as primarily a network/proxy-controlled service.

⚡ Reliability

Uptime/SLA
0
Version Stability
50
Breaking Changes
50
Error Recovery
30
AF Security Reliability

Use Cases

  • Provide Git access to clients that only have HTTP/HTTPS connectivity
  • Self-hosted Git endpoints for CI systems and automation
  • Use behind a reverse proxy or within environments where SSH is restricted

Not For

  • High-security environments that require strong user-level authorization beyond a network boundary (unless additional access controls are configured externally)
  • Workloads needing fine-grained per-repo or per-operation authz without external middleware
  • Use as a general-purpose Git hosting platform (issues, PRs, web UI, etc.)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
No
SDK
No
Webhooks
No

Authentication

Methods: HTTP basic auth / reverse-proxy auth (if configured externally) Network-based access control (IP allowlist / auth at gateway) Potential support for generic HTTP auth depending on configuration
OAuth: No Scopes: No

No explicit auth model (scopes/OAuth) is evident from the package name/description alone; security typically relies on server/reverse-proxy configuration.

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • Git-over-HTTP has protocol-specific endpoints and status behaviors; generic HTTP retry logic may not be appropriate for failed smart HTTP operations.
  • Authentication/authorization behavior may depend on external reverse-proxy configuration rather than the application itself.
  • Without a documented contract (e.g., OpenAPI), agents may need protocol knowledge to form correct requests.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for gitserver-http.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered