Git Remote URL (HTTPS) Regex for JavaScript
/^https://(?:[a-zA-Z0-9][a-zA-Z0-9\-]*\.)+[a-zA-Z]{2,63}/[a-zA-Z0-9_.\-]+/[a-zA-Z0-9_.\-]+(?:\.git)?$/iWhat this pattern does
This page provides a comprehensive, battle-tested regular expression for matching git remote url (https), ported and verified for JavaScript. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your JavaScript project — whether you're validating in an Express middleware, a Next.js API route, or a client-side form.
Javascript Implementation
// Git Remote URL (HTTPS)
// ReDoS-safe | RegexVault — Dev & Systems > Git
const gitRemoteUrlHttpsRegex = /^https:\/\/(?:[a-zA-Z0-9][a-zA-Z0-9\-]*\.)+[a-zA-Z]{2,63}\/[a-zA-Z0-9_.\-]+\/[a-zA-Z0-9_.\-]+(?:\.git)?$/i;
function validateGitRemoteUrlHttps(input: string): boolean {
return gitRemoteUrlHttpsRegex.test(input);
}
// Example
console.log(validateGitRemoteUrlHttps("https://github.com/user/repo")); // trueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
https://github.com/user/repo | git@github.com:user/repo.git |
https://github.com/org/repo.git | http://github.com/user/repo |
https://gitlab.com/group/project | https://github.com/user |
https://bitbucket.org/user/repo.git | github.com/user/repo |
https://git.example.com/team/project | — |
When to use this pattern
This pattern is drawn from the Dev & Systems > Git category and carries a ReDoS-safe certification. That matters for JavaScript developers because especially critical in long-running Node.js event loops where a ReDoS vulnerability can block the entire process. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.
Common Pitfalls
GitHub, GitLab, and Bitbucket accept HTTPS URLs without .git. Some git server implementations require it. Strip .git before display but preserve it for git operations.
Technical Notes
The .git suffix is optional on all major hosting platforms. HTTP (non-TLS) should be rejected for security. Always use HTTPS for remote operations.
Have a pattern that belongs in the vault?
Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.
Submit a Pattern