Gathering detailed insights and metrics for @azure/logger
Gathering detailed insights and metrics for @azure/logger
Gathering detailed insights and metrics for @azure/logger
Gathering detailed insights and metrics for @azure/logger
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/logger
Typescript
Module System
Min. Node Version
Node Version
94.2
Supply Chain
99.5
Quality
96.7
Maintenance
100
Vulnerability
100
License
@azure/arm-storageactions_1.0.0
Updated on Jul 11, 2025
@azure/core-xml_1.5.0
Updated on Jul 10, 2025
@azure-rest/core-client_2.5.0
Updated on Jul 10, 2025
@azure/core-client_1.10.0
Updated on Jul 10, 2025
@azure/core-sse_2.3.0
Updated on Jul 10, 2025
@azure/core-util_1.13.0
Updated on Jul 10, 2025
TypeScript (86.82%)
JavaScript (12.78%)
PowerShell (0.33%)
Bicep (0.05%)
HTML (0.01%)
Mustache (0.01%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
2,211 Stars
19,142 Commits
1,255 Forks
411 Watchers
656 Branches
3,042 Contributors
Updated on Jul 12, 2025
Latest Version
1.3.0
Package Id
@azure/logger@1.3.0
Unpacked Size
39.79 kB
Size
6.19 kB
File Count
20
Node Version
18.5.0
Published on
Jul 10, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
The @azure/logger
package can be used to enable logging in the Azure SDKs for JavaScript.
Logging can be enabled for the Azure SDK in the following ways:
DEBUG
environment variable.Note that AZURE_LOG_LEVEL, if set, takes precedence over DEBUG. Only use DEBUG without specifying AZURE_LOG_LEVEL or calling setLogLevel.
Install this library using npm as follows
1npm install @azure/logger
The @azure/logger
package supports the following log levels
specified in order of most verbose to least verbose:
When setting a log level, either programmatically or via the AZURE_LOG_LEVEL
environment variable,
any logs that are written using a log level equal to or less than the one you choose
will be emitted.
For example, setting the log level to warning
will cause all logs that have the log
level warning
or error
to be emitted.
NOTE: When logging requests and responses, we sanitize these objects to make sure things like Authorization
headers that contain secrets are not logged.
Request and response bodies are never logged. Headers are redacted by default, unless present in the following list or explicitly allowed by the client SDK:
1import { setLogLevel } from "@azure/logger"; 2 3setLogLevel("info");
1import { setLogLevel, AzureLogger } from "@azure/logger"; 2 3setLogLevel("verbose"); 4 5// override logging to output to console.log (default location is stderr) 6AzureLogger.log = (...args) => { 7 console.log(...args); 8};
Using AzureLogger
, it is possible to redirect the logging output from the Azure SDKs by
overriding the AzureLogger.log
method. This may be useful if you want to redirect logs to
a location other than stderr.
You can build and run the tests locally by executing rushx test
. Explore the test
folder to see advanced usage and behavior of the public classes.
If you run into issues while using this library, please feel free to file an issue.
If you'd like to contribute to this library, please read the contributing guide to learn more about how to build and test the code.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10
Reason
license file detected
Details
Reason
no dangerous workflow patterns detected
Reason
security policy file detected
Details
Reason
0 existing vulnerabilities detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
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 2025-07-07
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