Skip to main content
Critical: gitGost is designed for privacy-respecting contributions, not for evading accountability. Misuse will be detected and mitigated.
gitGost enforces strict policies and technical safeguards to prevent abuse. This page outlines prohibited uses and the consequences of violating them.

​
Prohibited Uses

​
Content-Related Violations

Malicious Code

Strictly prohibited:
  • Malware, ransomware, or spyware
  • Backdoors or security exploits
  • Code designed to harm or surveil users
  • Cryptojacking or resource hijacking scripts

Harmful Content

Strictly prohibited:
  • Sexually explicit material or pornography
  • Content sexualizing minors in any form
  • Promotion of violence, terrorism, or self-harm
  • Hate speech or discriminatory content

Illegal Material

Strictly prohibited:
  • Illegal weapons manufacturing instructions
  • Drug trafficking or distribution facilitation
  • Stolen intellectual property
  • Trade secret violations

Harassment & Abuse

Strictly prohibited:
  • Targeted harassment or doxxing
  • Defamation or impersonation
  • Coordinated abuse campaigns
  • Spam or automated flooding

​
Operational & Technical Abuse

You may NOT use gitGost to:
  • Bypass repository access controls or permissions
  • Evade bans or moderation actions
  • Circumvent rate limits through automated tools
  • Exploit vulnerabilities in target repositories
  • Use gitGost infrastructure for penetration testing
Consequence: Immediate hash blocking and potential legal action.
You may NOT use gitGost for:
  • Phishing attempts or credential theft
  • Identity theft or impersonation
  • False attribution or misleading contributions
  • Fraudulent claims or misrepresentation
  • Trojan contributions (innocent-looking code with hidden malicious intent)
Consequence: Hash blocking and coordination with law enforcement where applicable.
You may NOT use gitGost with:
  • Bots or automated PR generation scripts
  • Repository scrapers or spam tools
  • Coordinated flooding campaigns
  • Distributed abuse across multiple IPs
Consequence: Rate limiting, IP blocking, and service-wide panic mode activation.
Legal Responsibility:By using gitGost, you declare that your contribution:
  1. Is your original work or properly licensed
  2. Does not infringe third-party intellectual property
  3. Does not violate confidentiality or trade secret agreements
  4. Complies with applicable laws in your jurisdiction and Mexico
You bear sole legal responsibility for this declaration. See LEGAL.md for full terms.

​
Abuse Prevention Measures

gitGost implements multiple layers of protection against misuse:

​
Rate Limiting

Per-IP Limits

5 PRs per IP per hourPrevents spam flooding while allowing legitimate rapid contributions. Resets hourly.

​
Size Constraints

Repository Size

Maximum: 500 MBPrevents abuse of gitGost for hosting large datasets or binaries.

Commit Size

Maximum: 10 MBBalances legitimate contributions with Tor network compatibility.

​
Validation & Sanitization

Every push is validated for:
  • Valid Git refs: Ensures proper branch/tag formatting
  • Object integrity: Checks for corrupted or malformed Git objects
  • Commit structure: Validates author/committer fields are properly stripped
  • Repository accessibility: Confirms target repo exists and accepts PRs
gitGost automatically removes:
  • Author name and email from commits
  • Committer name and email
  • Original timestamps (replaced with current time)
  • GPG signatures and signed commits
  • Custom Git headers and trailers
All PRs are created by the neutral @gitgost-anonymous bot account.

​
Emergency Response

Panic Mode

If abusive activity is detected, administrators can:
  • Suspend the service immediately (all pushes rejected)
  • Close recent PRs in bulk (2-hour rollback window)
  • Block contribution hashes from future submissions
  • Display public warnings on the service website
See Service Administration for details.

​
Consequences of Abuse

​
Immediate Actions

  1. Hash Blocking: The commit hash is permanently blocked from making future submissions
  2. Rate Limit Enforcement: IP-based throttling prevents rapid retry attempts
  3. PR Rejection: The malicious PR is immediately closed or never created

​
Escalation Path

1

Detection

Abuse detected through rate limits, validation failures, or manual reports
2

Mitigation

Hash blocked, service suspended if widespread, affected PRs closed
3

Investigation

Logs reviewed (within 2-hour retention window), patterns identified
4

Legal Action

For serious violations (malware, harassment, fraud), coordination with:
  • GitHub Trust & Safety
  • Law enforcement (if criminal activity)
  • Copyright holders (for DMCA violations)

​
DMCA & Intellectual Property Claims

If you believe content submitted through gitGost infringes your intellectual property:Contact: [email protected] with subject [DMCA] or [IP-CLAIM]Include:
  1. Identification of your copyrighted work
  2. PR URL, commit hash, or repository link
  3. Your contact information
  4. Good-faith statement and declaration under penalty of perjury
Response time:
  • Acknowledgment within 5 business days
  • Action taken within 10 business days
Action: Contribution hash blocked, PR closure requested from target repositorySee LEGAL.md for full procedures.

​
What Makes a Contribution Appropriate?

Ask yourself:✅ Would I make this contribution under my real name if I felt safe doing so?
✅ Does this contribution improve the project in good faith?
✅ Am I respecting the maintainer’s time and the community’s norms?
✅ Is my only concern the privacy of my identity, not evading consequences?If you answered yes to all four questions, gitGost is appropriate for your use case.

​
Good vs. Bad Anonymity

✅ Appropriate Use❌ Inappropriate Use
Fixing typos without public recordSubmitting spam PRs
Contributing despite employer restrictionsEvading repository bans
Protecting identity in hostile jurisdictionHarassing maintainers
Experimenting without social pressureInjecting malicious code
Avoiding email harvestingCircumventing contribution agreements

​
Reporting Abuse

If you observe abusive use of gitGost:

Email Report

Email: [email protected]
Subject: [ABUSE]Include PR URL, repository, and description of abuse.

Anonymous Report

GitHub Issue: Open with prefix [LEGAL] or [ABUSE]Reports can be made anonymously through throwaway accounts.

​
Why These Rules Exist

Protecting the Service

gitGost exists to serve legitimate privacy needs, not to enable harm. Strict abuse prevention:
  • Keeps the service operational for those who need it
  • Prevents legal liability for the project maintainers
  • Maintains trust with repository maintainers and the GitHub platform
  • Ensures gitGost doesn’t become a vector for coordinated attacks
Every abuse incident risks shutting down the service for everyone. Use it responsibly.

Legitimate Uses

Learn when gitGost is the right tool for your contribution

Build docs developers (and LLMs) love

Get started for freeTalk to us