Gathering detailed insights and metrics for azure-devops-node-api
Gathering detailed insights and metrics for azure-devops-node-api
Gathering detailed insights and metrics for azure-devops-node-api
Gathering detailed insights and metrics for azure-devops-node-api
azure-devops-node-utilities
Utilities for use with azure-devops-node-api and azure-pipelines-task-lib.
@xiaoxu_dev/azure-devops-node-api
Node client for Azure DevOps and TFS REST APIs
@starkmsu/azure-devops-node-api
Node client for Azure DevOps and TFS REST APIs
@axosoft/azure-devops-node-api
Node client for Azure DevOps and TFS REST APIs
Azure DevOps Client for Node.js
npm install azure-devops-node-api
Typescript
Module System
Min. Node Version
Node Version
NPM Version
TypeScript (99.5%)
JavaScript (0.5%)
Total Downloads
77,619,432
Last Day
40,458
Last Week
660,782
Last Month
3,026,582
Last Year
28,117,994
NOASSERTION License
488 Stars
311 Commits
236 Forks
100 Watchers
72 Branches
135 Contributors
Updated on Jul 15, 2025
Latest Version
15.1.0
Package Id
azure-devops-node-api@15.1.0
Unpacked Size
4.63 MB
Size
570.10 kB
File Count
164
NPM Version
8.19.4
Node Version
16.20.2
Published on
May 15, 2025
Cumulative downloads
Total Downloads
Last Day
-10.6%
40,458
Compared to previous day
Last Week
-12.7%
660,782
Compared to previous week
Last Month
2.6%
3,026,582
Compared to previous month
Last Year
33.4%
28,117,994
Compared to previous year
2
Integrate with Azure DevOps from your Node.js apps.
npm install azure-devops-node-api --save
vso-node-api has been renamed and released as azure-devops-node-api
See samples for complete coding examples
npm install azure-devops-node-api --save
1import * as azdev from "azure-devops-node-api"; 2 3// your collection url 4let orgUrl = "https://dev.azure.com/yourorgname"; 5 6let token: string = process.env.AZURE_PERSONAL_ACCESS_TOKEN; 7 8let authHandler = azdev.getPersonalAccessTokenHandler(token); 9let connection = new azdev.WebApi(orgUrl, authHandler);
Please note that some API's (e.g. ProfileApi) can't be hit at the org level, and has to be hit at the deployment level, so url should be structured like https://vssps.dev.azure.com/{yourorgname}
1import * as ba from "azure-devops-node-api/BuildApi"; 2 3let build: ba.IBuildApi = await connection.getBuildApi();
These clients are available:
Coding is easy using linear coding with async/await in TypeScript
1import * as bi from "azure-devops-node-api/interfaces/BuildInterfaces"; 2 3async function run() { 4 let project: string = "myProject"; 5 let defs: bi.DefinitionReference[] = await build.getDefinitions(project); 6 7 defs.forEach((defRef: bi.DefinitionReference) => { 8 console.log(`${defRef.name} (${defRef.id})`); 9 }); 10} 11 12run();
To see what APIs are available, see the appropriate client interface. For example, GitApi.ts
More detailed information for the endpoints of each API can be found at https://docs.microsoft.com/en-us/rest/api/vsts/?view=vsts-rest-4.1
Pre-reqs: Node >= 16 and typescript (tsc) >= 4
Run npm install
first
Set environment variables using set or export:
1API_URL=https://dev.azure.com/yourorgname 2 3// use your token 4API_TOKEN=cbdeb34vzyuk5l4gxc4qfczn3lko3avfkfqyb47etahq6axpcqha 5 6API_PROJECT=myProject
Run samples:
1$ npm run samples
Run a specific sample:
1$ npm run samples -- projectAnalysis
v14 and above - [current, maintained] - Supports node 16 and above
v13 and below - End Of Life, for Node < 16, contains security vulnerabilities, use at your own risk
Below you'll find a quick mapping of azure-devops-node-api versions and their corresponding TFS releases. All API versions will work on the TFS version mentioned as well as later TFS versions.
TFS Version | Node API VERSION |
---|---|
Azure DevOps Server vNext | 8.0.0 |
Azure DevOps Server 2019 | 7.0.0 |
TFS 2018 Update 2 | 6.6.2 |
TFS 2017 Update 2 | 6.2.8-preview |
TFS 2017 Update 1 | 5.1.2 |
TFS 2017 RTW | 5.0.0 |
TFS 2015 Update 2 | 0.7.0 |
To contribute to this repository, see the contribution guide
Feel free to file an issue in this repo.
Do you think there might be a security issue? Have you been phished or identified a security vulnerability? Please don't report it here - let us know by sending an email to secure@microsoft.com.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
10 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
license file detected
Details
Reason
1 existing vulnerabilities detected
Details
Reason
branch protection is not maximal on development and all release branches
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-14
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More