Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.3

FindBugs Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: FindBugs is software used to look for potential bugs in Java programs. This technology is based on the concept of bug patterns. A bug pattern is a code idiom that is often an error. FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. Static analysis means that this technology can find bugs by inspecting a program`s code. Executing the program is not necessary for this technology to find potential bugs. This technology has two interfaces: a graphical user interface (GUI) and a command line user interface.

This technology does not utilize a database to store data, as any data generated by this technology is saved to the user`s local drive.

Note: FindBugs can run as a standalone application or a plugin within another applications such as Maven or Eclipse.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.12
Decision Date: 12/03/2020 at 22:38:30 UTC
Introduced By: Extended Tool List (ETL)
Vendor Name: Bill Pugh
- The information contained on this page is accurate as of the Decision Date (12/03/2020 at 22:38:30 UTC).