Gathering detailed insights and metrics for @azure/core-http-compat
Gathering detailed insights and metrics for @azure/core-http-compat
Gathering detailed insights and metrics for @azure/core-http-compat
Gathering detailed insights and metrics for @azure/core-http-compat
This repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js.
npm install @azure/core-http-compat
@azure/arm-terraform_1.0.0-beta.1
Published on 28 Nov 2024
@azure/arm-connectedcache_1.0.0-beta.1
Published on 28 Nov 2024
@azure/core-rest-pipeline_1.18.1
Published on 26 Nov 2024
@azure/arm-networkcloud_2.0.0-beta.1
Published on 26 Nov 2024
@azure/arm-apimanagement_9.2.0
Published on 26 Nov 2024
@azure/template_1.0.13-beta.4363791
Published on 26 Nov 2024
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
2,095 Stars
17,466 Commits
1,209 Forks
357 Watching
460 Branches
2,703 Contributors
Updated on 28 Nov 2024
TypeScript (86.72%)
JavaScript (12.89%)
PowerShell (0.32%)
Bicep (0.05%)
HTML (0.01%)
Mustache (0.01%)
Cumulative downloads
Total Downloads
Last day
4.6%
438,575
Compared to previous day
Last week
0.5%
2,398,815
Compared to previous week
Last month
0.1%
10,313,959
Compared to previous month
Last year
138.4%
84,605,622
Compared to previous year
This repository is for the Azure SDK for JavaScript (Node.js & Browser). It contains libraries for the breadth of Azure services. Management libraries are packages that you would use to provision and manage Azure resources. Client libraries are packages that you would use to consume these resources and interact with them.
A few helpful resources to get started are:
/sdk
folder of this repository. The same readme file can be found on the landing page for the package in npm.Each service might have a number of libraries available from each of the following categories:
NOTE: Some of these packages have beta versions. If you need to ensure your code is ready for production, use one of the stable, non-beta packages.
Given an Azure resource already exists, you would use the client libraries to consume it and interact with it. Most of these libraries follow the Azure SDK Design Guidelines for JavaScript & TypeScript and share a number of core functionalities such as retries, logging, transport protocols, authentication protocols, etc. Others will be updated in the near future to follow the guidelines as well.
To get a list of all client libraries that follow the new guidelines, please visit our Azure SDK releases page.
Management libraries enable you to provision and manage Azure resources via the Azure Resource Manager i.e. ARM. You can recognize these libraries by @azure/arm-
in their package names. These are purely auto-generated based on the swagger files that represent the APIs for resource management.
Newer versions of these libraries follow the Azure SDK Design Guidelines for TypeScript. These new versions provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. A few helpful resources to get started with these are:
NOTE: If you are experiencing authentication issues with the management libraries after upgrading certain packages, it's possible that you upgraded to the new versions of SDK without changing the authentication code, please refer to the migration guide mentioned above for proper instructions.
azure-sdk-js
tag.Try our community resources.
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) secure@microsoft.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
For details on contributing to this repository, see the contributing guide.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.
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
30 commit(s) and 16 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
Reason
GitHub workflow tokens follow principle of least privilege
Details
Reason
security policy file detected
Details
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
binaries present in source code
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
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Score
Last Scanned on 2024-11-25
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