Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 26.1

JavaScript

General Information

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:	JavaScript (often shortened to JS) is a high-level, interpreted, object-oriented language with first-class functions. This standard is best known as the scripting language for web pages, but the language is used in many non-browser environments as well. JavaScript runs on the client-side of the web, which can be used to design/program how web pages behave on the occurrence of an event. JavaScript is primarily used to enhance Hypertext Markup Language (HTML) pages and is commonly found embedded in HTML code. JavaScript renders web pages in an interactive and dynamic fashion, which allows the pages to do a variety of things, including react to events, exhibit special effects, accept variable text, validate data, create cookies, and detect a user`s browser. JavaScript is the colloquial term for vendor-specific implementations of the scripting language that the European Computer Manufacturers Association (ECMA) body maintains as ECMAScript. Therefore, this forecast is based on the ECMA standard. JavaScript was formalized in the ECMAScript language standard and is primarily used as part of a web browser (client-side JavaScript). This enables programmatic access to objects within a host environment. ECMAScript is supported in many applications, especially web browsers, where it is implemented by JavaScript. Implementations sometimes include extensions to the language, or to the standard library and related application programming interfaces (API) such as the World Wide Web Consortium (W3C) specified Document Object Model (DOM). This means that applications written in one implementation may be incompatible with another, unless they are written to use only a common subset of supported features and APIs.
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 System Security Officer (ISSO), 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:
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v26.1
Decision Date:	01/15/2026 at 00:15:40 UTC
Aliases:	ECMAScript
Introduced By:	Enterprise Program Management Office (EPMO) TRM Team
Standards Body:	ECMA
Cage Code:	N/A

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Industry Standard, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Major versions and minor versions of that Major released on or after 09/14/2022 are NOT EXEMPT. Major Versions released before 09/14/2022 are EXEMPT as well as minor versions of that Major regardless of release date.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
Edition 1	06/01/1997
Edition 2	08/01/1998
Edition 3	12/01/1999
Edition 5	12/01/2009
Edition 5.1	06/01/2011
Edition 6	06/17/2015
Edition 7	06/17/2016
Edition 8	06/01/2017
Edition 9	06/01/2018
Edition 10	06/01/2019
Edition 13	06/01/2022
Edition 15	06/01/2024
Edition 16	06/01/2025

Current Decision Matrix (01/12/2026)

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 System Security Officer (ISSO), 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.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unauthorized, Conditions Required^[a] : This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Unauthorized, Conditions Required^[b] : VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Unauthorized, Conditions Required^[c] : The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Unauthorized, Conditions Required ^[a] .

Release	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
<Past	CY2025				CY2026				CY2027				Future>
Edition 3	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 5	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 5.1	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 6	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 7	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 8	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 9	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 10	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 13	Authorized w/ Constraints (DIVEST)	Authorized w/ Constraints (DIVEST)	Authorized w/ Constraints (DIVEST)	Authorized w/ Constraints (DIVEST)	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 15	Authorized	Authorized	Authorized	Authorized	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[b]	Unauthorized, Conditions Required^[a]	Unauthorized, Conditions Required^[a]
Edition 16	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized w/ Constraints (POA&M)	Authorized	Authorized	Authorized	Authorized	Authorized	Authorized	Authorized	Authorized
Note:	At the time of writing, Edition 16 is the most current version, released 06/01/2025.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Source	Name	Description
No components have been identified for this entry.


Application Technology Development Tools	Application Development Tools

General Analysis

Adoption Benefits

This standard is supported by all modern web browsers without the need for plugins.
This is a widely used standard.
This standard has a comprehensive set of documentation.

Adoption Risks

A common JavaScript-related security problem is cross-site scripting (XSS), a violation of the same-origin policy. XSS vulnerabilities occur when an attacker is able to cause a target web site to include a malicious script in the webpage presented to a victim. Some browsers include partial protection against reflected XSS attacks, in which the attacker provides a Uniform Resource Locator (URL) including malicious script. However, even users of those browsers are vulnerable to other XSS attacks, such as those where the malicious code is stored in a database. Only correct design of web applications on the server-side can fully prevent XSS.
Due to JavaScript running in widely varying environments, an important part of testing and debugging is to test and verify that it works across multiple browsers.
JavaScript is a loosely typed language. Loose typing places a major responsibility for static type management on programmer discipline, very little on the compiler, and late reporting of type safety violation on the run-time. The result is a development environment where type bugs can be easily introduced due to human fallibility. The bugs may be difficult to detect or may go undetected by the run-time.

Architectural Benefits

This standard supports both client and server-side web applications. This standard is most commonly used as part of web browsers, whose implementations allow client-side scripts to interact with the user, control the browser, communicate asynchronously, and alter the document content that is displayed. It can also be used in server-side network programming, and the creation of desktop and mobile applications.

- The information contained on this page is accurate as of the Decision Date (01/15/2026 at 00:15:40 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 26.1

General Information

Vendor Release Information

Current Decision Matrix (01/12/2026)

References

Standard Components

VA Categories

View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 26.1

General Information

Vendor Release Information

Current Decision Matrix (01/12/2026)

References

Standard Components

VA Categories View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES

VA Categories

View the VA Categorization Framework