Rules
Navigation
Purpose
Git Glimpse allows registered users to generate public, read-only snapshots of private GitHub repositories for easy sharing.
It is not a backup service and does not provide Git history.
What Gets Shared
- Only the default branch (latest state) is included
- Submodules are not supported
- Only files present at build time are included
- All content becomes publicly accessible via the generated link.
Access & Visibility
Snapshots are publicly accessible to anyone with the link
No authentication is required to view shared content
Do not upload repositories containing secrets or sensitive data
The service does not scan for secrets
You are fully responsible for the content you share.
Repository Limits
Per repository build:
- Maximum repository size: 100 MB
- Maximum file size (included): 10 MB
- Maximum files: 10,000
- Maximum directories: 5,000
- Maximum directory depth: 20
- Maximum clone time: 30 seconds
- Maximum scan time: 10 seconds
- Maximum render time: 20 seconds
Files exceeding limits may be skipped or cause the build to fail.
Forbidden File Types:
Repositories cannot include the following special file types:
- Symbolic links
- FIFO/Named pipes
- Character devices
- Block devices
- Sockets
Attempting to add these will result in a build error.
Account Lifetime
A repository snapshot remains available as long as the owner's account is active.
Accounts are flagged inactive after 90 days of inactivity; user will recieve a warning email.
After 97 days, repositories are marked hidden and become inaccessible.
Account removal deletes all associated repository data.
Rebuilds
Snapshots are created only when the owner triggers a build
Content does not update automatically when the source repository changes
Each build replaces the previous snapshot
Acceptable Use
You agree not to use Git Glimpse to share:
- Illegal content
- Malware or exploit code intended for harm
- Content you do not have the right to distribute
- Personal data without consent
Accounts violating these rules may be suspended and data removed.
Security Model
Access to private repositories is performed using user-provided deploy keys
Keys are stored encrypted and used only for cloning
The service operates in an isolated build environment
No Warranty
Git Glimpse is provided as-is without guarantees of:
- Availability
- Data durability
- Fitness for any particular purpose
Always keep your own backups.