Open Source JavaScript Version Control Software
Sort By:
JavaScript Version Control Software
View 80 business solutionsBrowse free open source JavaScript Version Control Software and projects below. Use the toggles on the left to filter open source JavaScript Version Control Software by OS, license, language, programming language, and project status.
-
Build Agents and Models on One PlatformGemini Enterprise Agent Platform is Google Cloud's comprehensive platform for developers to build, scale, govern, and optimize agents and models. Choose from Google's most advanced models and third-party models like Anthropic's Claude Model Family.
-
MongoDB Atlas runs apps anywhereMongoDB Atlas gives you the freedom to build and run modern applications anywhere—across AWS, Azure, and Google Cloud. With global availability in over 115 regions, Atlas lets you deploy close to your users, meet compliance needs, and scale with confidence across any geography.
-
1
ungit
A tool to simplify the use of git, on any platform, anywhere
Git is known for being a versatile distributed source control system that is a staple of many individuals, communities, and even for the City of Chattanooga to crowd source bicycle parking locations. However, it is not known for userfriendliness or easy learning curve. Ungit brings user friendliness to git without sacrificing the versatility of git. Git and github both supports PGP signing. Within Ungit these features can be enabled. Currently, Ungit DOES NOT support GPG authentication! While git allows robust programmatic authentication via credential-helper, I could not find an easy way to do something equivalent with GPG. Therefore, password-less gpg authentication or 3rd party gpg password must be configured when using Ungit to commit with gpg. Ungit will watch git directory recursively upon page view and automatically refresh contents on git operations or changes on files that are not configured to be ignored in .gitignore. -
2
Husky
Git hooks made easy
Husky is a tool that makes handling Git hooks a lot easier, and lets you run the scripts you want at those stages. It works by including an object right within your package.json file. This then configures Husky so that it runs the scripts you specify. After that, it's Husky's responsibility to manage at which point in the Git lifecycle your scripts will run. Husky helps to improve your commits, lets you run tests, lint code and more when you commit or push. It is very lightweight, with zero dependencies and is capable of supporting all Git hooks. -
3
NodeGit
Native Node bindings to Git
Asynchronous native Node bindings to libgit2. NodeGit will work on most systems out-of-the-box without any native dependencies. If you receive errors about libstdc++, which are commonly experienced when building on Travis-CI, you can fix this by upgrading to the latest libstdc++-4.9. If you wish to help contribute to NodeGit it is useful to build locally. If you encounter errors, you most likely have not configured the dependencies correctly. You will need libpcre, libpcreposix, libkrb5, libk5crypto, and libcom_err libraries installed on your Linux machine. When building locally, you will also need development packages for kerberos and pcre, so both pcre-config, and krb5-config utilities must be present on your machine. -
4
lint-staged
Run linters on git staged files
Run linters against staged git files and don't let anything slip into your code base! Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. This project contains a script that will run arbitrary shell tasks with a list of staged files as an argument, filtered by a specified glob pattern. Linter commands work on a subset of all staged files, defined by a glob pattern. lint-staged uses micromatch for matching files. The concept of lint-staged is to run configured linter tasks (or other tasks) on files that are staged in git. lint-staged will always pass a list of all staged files to the task, and ignoring any files should be configured in the task itself. -
Custom VMs From 1 to 96 vCPUs With 99.95% UptimeLive migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
-
5
Commitizen for contributors
The commitizen command line utility
When you commit with Commitizen, you'll be prompted to fill out any required commit fields at commit time. No more waiting until later for a git commit hook to run and reject your commit (though that can still be helpful). No more digging through CONTRIBUTING.md to find what the preferred format is. Get instant feedback on your commit message formatting and be prompted for required fields. Commitizen is currently tested against Node.js 12, 14, & 16, although it may work in older versions of Node.js. You should also have npm 6 or greater. When you're working in a Commitizen-friendly repository, you'll be prompted to fill in any required fields, and your commit messages will be formatted according to the standards defined by project maintainers. Installing and running Commitizen locally allows you to make sure that developers are running the exact same version of Commitizen on every machine. -
6
Conventional Changelog
Generate changelogs and release notes from a project's commit messages
The conventional-changelog repo is managed as a monorepo; it's composed of many npm packages. It's recommended you use the high-level standard-version library, which is a drop-in replacement for npm's version command, handling automated version bumping, tagging, and CHANGELOG generation. Alternatively, if you'd like to move towards completely automating your release process as an output from CI/CD, consider using semantic-release. We specifically limit our support to LTS versions of Node, not because this package won't work on other versions, but because we have a limited amount of time, and supporting LTS offers the greatest return on that investment. It's possible this package will work correctly on newer versions of Node. It may even be possible to use this package on older versions of Node, though that's more unlikely as we'll make every effort to take advantage of features available in the oldest LTS version we support. -
7
git-sketch-plugin
A Git client generating pretty diffs built right into Sketch
A Git client generating pretty diffs built right into Sketch. A Git client built right into Sketch. The plugin really improves the review process by exporting an image for every part of the design. Every member of the team can quickly see what the next iteration will change through Github’s interface. Each step of the design process is now documented. Newcomers are able to understand how we ended up with the current iteration and why we went with some options and not others. Create a new branch when you start working on a new feature. Work normally on your design. Save the file. Commit the changes with a meaningful message describing them. The plugin will extract the artboards in your file in order to show the differences easily. Push your changes to the remote. Create a pull request from your branch to the master branch. Voila. Your co-workers can review the changes, comment on them and approve them. Once approved, merge the pull request. -
8
pretty-quick
Get Pretty Quick
Runs Prettier on your changed files. Pre-commit mode. Under this flag only staged files will be formatted, and they will be re-staged after formatting. Partially staged files will not be re-staged after formatting and pretty-quick will exit with a non-zero exit code. The intent is to abort the git commit and allow the user to amend their selective staging to include formatting fixes. When not in staged pre-commit mode, use this flag to compare changes with the specified branch. Defaults to master (git) / default (hg) branch. Do not resolve prettier config when determining which files to format, just use standard set of supported file types & extensions prettier supports. This may be useful if you do not need any customization and see performance issues. Check that files are correctly formatted, but don't format them. This is useful on CI to verify that all changed files in the current branch were correctly formatted. -
9
isomorphic-git
A pure JavaScript implementation of git for node and browsers!
A pure JavaScript implementation of git for node and browsers! Clone repos, create commits, push branches and more in client-side JS. It uses the same on-disk format as git so it works with existing repos. isomorphic-git is a pure JavaScript implementation of git that works in node and browser environments (including WebWorkers and ServiceWorkers). This means it can be used to read and write to git repositories, as well as fetch from and push to git remotes like GitHub. isomorphic-git aims for 100% interoperability with the canonical git implementation. This means it does all its operations by modifying files in a ".git" directory just like the git you are used to. The included isogit CLI can operate on git repositories on your desktop or server. isomorphic-git aims to be a complete solution with no assembly required. The API has been designed with modern tools like Rollup and Webpack in mind. -
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
10
simple-git-hooks
A simple git hooks manager for small projects
A simple git hooks manager for small projects. A git hook is a command or script that is going to be run every time you perform a git action, like git commit or git push. If the execution of a git hook fails, then the git action aborts. For example, if you want to run linter on every commit to ensure code quality in your project, then you can create a pre-commit hook that would call npx lint-staged. Check out lint-staged. It works really well with simple-git-hooks. You can look up about git hooks on the Pro Git book. simple-git-hooks works well for small-sized projects when you need quickly set up hooks and forget about it. However, this package requires you to manually apply the changes to git hooks. If you update them often, this is probably not the best choice. Also, this package allows you to set only one command per git hook. -
11
ghooks
Simple git hooks
Simple git hooks. It is not advised to install ghooks as a production dependency, as it will install git hooks in your production environment as well. Please install it under the devDependencies section of your package.json. Please also note, that it is absolutely not advised to install ghooks globally. To work as expected, make it a development dependency of your project(s). Add a config.ghooks entry in your package.json and simply specify which git hooks you want and their corresponding commands. The hooks' working directory is relative to the git root (where you have your .git directory). This means that if your package.json is in a subdirectory of your git repository, you'll need to cd into the directory before running any npm scripts. -
12
Provide secure and stable OS, based on highly modified Linux Kernel, own package system, like "BSD Ports". Compatible with x86, Power PC. Easy to use of any level users. Complete Documentantion in many languages. 99% compatible with Windows.
-
13
The iF.SVNAdmin application is a web based GUI to your Subversion authorization file. It is based on PHP 5.3 and requires a web server (Apache) to be installed. (+ LDAP integration; no database required)
-
14
It's a web application which provides a unify solution to stat. CVS/SVN repository modules code change information and generate html reports. User can browse line of change, file of change, code diff, check-in comment and so on, it can stat. more repository modules one time. After repository modules configured, stat. is simple like a search.
-
15
phpEasyVCS
File based version control system written in PHP
phpEasyVCS is a simple version control system (VCS) with minimal hosting requirements, namely PHP 5.2+. No database is needed. Files can be viewed and uploaded with a browser or by WebDAV, which allows you to access the files like a local drive in all operating systems. For integration with other software a REST service is provided. It is very easy to view the file versions at a specific point in time. The web interface allows you to easily compare file versions and synchronize and merge local files with the files in phpEasyVCS. It is possible to host multiple repositories and define multiple users with full, read-only or no access to each of the repositories. -
16
Stat cvs/svn Code Change
stat. cvs,svn code changes and generate html report
It's a web application which provides a unify solution to stat. CVS/SVN repository modules code change information and generate html reports. User can browse line of change, file of change, code diff, check-in comment and so on, it can stat. more repository modules one time. After repository modules configured, stat. is simple like a search. It's the mirror project of CodeChangeViewer: http://sourceforge.net/projects/ccv/. -
17
Web based PDM/PLM solution. Modules to include: Document Management, Lifecycle Management, Workflow System, Change Management, Product Configuration System, Product Numbering System, CAx Integration, CAx File Viewer System
-
18
Codepot
Web-based subversion manager
Codepot is a web-based subversion repository manager. It incorporates the subversion revision control system and wiki-based documentation, and supports authentication via LDAP or DBMS. If you opt for the simplest, you can manage multiple subversion repositories independent of each other. Going beyond it, you can track issues, write documents, and upload release files. See it live at http://code.abiyo.net -
19
Mole is a project started in 2008, designed for allowing users to easily share all kinds of ressources. It is planned to be used as a Mozilla Firefox extension.
-
20
All Node.js versions
List all available Node.js versions
List all available Node.js versions. Sorted from the most to the least recent. Includes major release and LTS information. This package is an ES module and must be loaded using an import or import() statement, not require(). The return value resolves to an object with the following properties. List of available Node.js versions and related information. Sorted from the most to the least recent Node.js version. List of Node.js major releases sorted from the most to the least recent. -
21
Group project to develop a campground reservation system as part of a Software Engineering class requirement.
-
22
CodeForge is a web based management application that helps to develop and maintain IT projects. THIS PROJECT IS A PROTOTYPE and further work on it has been stopped. A proper project is hosted by the Google Code with the same name.
-
23
Colimas is a Component Library Management System. The objective is to store all reusable resets for enterprises or organizations and to help all developers to know where and how to get the needed components and reduce understanding time for project maint
-
24
Digital Archive and Retrieval Tool (DART) presents engineers with an easy to use alternative to typical SVN or other CVS type systems. It allows engineers to easily archive data and provides an interface for managing and accessing store information.
-
25
Deploid is a web-based resource deployment management system for managing resources in a multi-tiered web environment. It leverages the use of versioning control software to efficiently push resources to testing and production environments.
