Chora is built upon the Horde Application Framework and provides a read-only browser interface to any number of version control repositories. Advanced features include a visual branch view of the repository's history, pretty-printed output, annotation, patchsets and basic statistics.
Cvsplot is a Perl script which analyzes the history of a CVS-managed project. The script executes on a set of files, analyzes their history, and automatically generates graphs that plot lines of code, number of files, and user contributions against time. It supports both UNIX and Windows environments.
Anthill is a tool that ensures a controlled build process and promotes the sharing of knowledge within an organization. Anthill performs a checkout from the source repository of the latest version of a project before every build and tags the repository with a unique build number after every build. It supports many reposistory adapters including: CVS (Concurrent Versions System), Visual Source Safe, Perforce, PVCS, StarTeam, MKSIntegrity, and FileSystem. Anthill also automatically updates a project intranet site with artifacts from the latest build. Anthill is an extension to the Apache-Ant project and is compatible with version 1.3, 1.4, and 1.5 of Ant.
Codestriker is a Web application that supports online code reviews. Traditional document reviews are supported, as well as reviewing diffs generated by an SCM (Source Code Management) system and plain unidiff patches. There are integration points with CVS, Subversion, Clearcase, Perforce, Visual SourceSafe, and Bugzilla. There is a plug-in architecture for supporting other SCMs and issue tracking systems. It minimizes paper work, ensures that issues, comments, and decisions are recorded in a database, and provides a comfortable workspace for actually performing code inspections. An optional highly-configurable metrics subsystem allows you to record code inspection metrics as a part of your process.
cvs-importer automates the task of importing all past versions of an existing project into CVS or Subversion, including automatically removing generated files, creating .cvsignore files/svn:ignore properties, and tagging each version. Thus, you can gain some of the advantages of scm for the older versions that weren't actually developed in cvs/svn, by having all the changes in the history.