npmpackage.info

@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.

1.1.4

2,118

MIT

TypeScript

1.11 kB

446,360,807 7.2

Installations

npm install @azure/logger

Developer Guide

BETA

Typescript

Yes

Module System

ESM, UMD

Min. Node Version

>=18.0.0

Node Version

18.5.0 Score

98.1

Supply Chain

100

Quality

96.7

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

116

Total

23,806

Closed

7,032

Merged

16,658

Issues

Open

663

Total

9,068

Closed

8,405

Releases

3,485

@azure/core-http-compat_2.2.0

Published on 06 Feb 2025

@azure/core-rest-pipeline_1.19.0

Published on 06 Feb 2025

@azure/core-amqp_4.3.5

Published on 06 Feb 2025

@azure-rest/core-client_2.3.3

Published on 06 Feb 2025

@azure/communication-chat_1.6.0-beta.4

Published on 04 Feb 2025

@azure/monitor-opentelemetry_1.8.1

Published on 01 Feb 2025

View all 3,485 releases

Contributors

2,791

View all 2,791 contributors

Languages

TypeScript

JavaScript

PowerShell

Bicep

HTML

Mustache

CSS

Batchfile

Dockerfile

Shell

Handlebars

SCSS

Vue

TypeScript (86.62%)

JavaScript (12.97%)

PowerShell (0.32%)

Bicep (0.05%)

HTML (0.01%)

Mustache (0.01%)

Love this project? Help keep it running — sponsor us today! 🚀

Developer

Azure

Download Statistics

Total Downloads

446,360,807

Last Day

1,021,958

Last Week

3,495,169

Last Month

20,149,725

Last Year

208,050,532

GitHub Statistics

2,118 Stars

18,086 Commits

1,217 Forks

377 Watching

516 Branches

2,791 Contributors

Bundle Size

2.44 kB

Minified

1.11 kB

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

1.1.4

Package Id

@azure/logger@1.1.4

Unpacked Size

127.81 kB

Size

15.12 kB

File Count

Node Version

18.5.0

Publised On

02 Aug 2024

Total Downloads

Cumulative downloads

Total Downloads

446,360,807

Last day

2.2%

1,021,958

Compared to previous day

Last week

-23%

3,495,169

Compared to previous week

Last month

24.1%

20,149,725

Compared to previous month

Last year

60.1%

208,050,532

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

tslib

Dev Dependencies

@azure/dev-tool @azure/eslint-plugin-azure-sdk @microsoft/api-extractor @types/node @vitest/browser @vitest/coverage-istanbul dotenv eslint playwright rimraf tshy typescript vitest

Versions

Azure SDK for JavaScript

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.

Getting started

A few helpful resources to get started are:

The readme for each package contains code samples and package information. This readme can be found in the corresponding package folder under the folder of the service of your choice in the /sdk folder of this repository. The same readme file can be found on the landing page for the package in npm.
The API reference documentation of the latest versions of these packages, can be found at our public developer docs.
The API reference documentation of older versions, can be found in our versioned developer docs.

Each service might have a number of libraries available from each of the following categories:

Client
Management

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.

Client

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

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:

List of management libraries that follow the new guidelines
Documentation and code samples.
Migration guide that shows how to transition from older versions of libraries.

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.

Need help?

For detailed documentation, visit our Azure SDK for JavaScript documentation
File an issue via GitHub Issues
Check previous questions or ask new ones on StackOverflow using azure-sdk-js tag.
Read our Support documentation.

Community

Try our community resources.

Reporting security issues and security bugs

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.

Contributing

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.

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

Maintained

Determines if the project is "actively maintained".

10

License

Determines if the project has defined a license.

10

Security-Policy

Determines if the project has published a security policy.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

9

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

4

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

SAST

Determines if the project uses static code analysis.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/event-processor.yml:158: update your workflow using https://app.stepsecurity.io/secureworkflow/Azure/azure-sdk-for-js/event-processor.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/event-processor.yml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/Azure/azure-sdk-for-js/event-processor.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/event-processor.yml:99: update your workflow using https://app.stepsecurity.io/secureworkflow/Azure/azure-sdk-for-js/event-processor.yml/main?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/event.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/Azure/azure-sdk-for-js/event.yml/main?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/scheduled-event-processor.yml:126: update your workflow using https://app.stepsecurity.io/secureworkflow/Azure/azure-sdk-for-js/scheduled-event-processor.yml/main?enable=pin
Warn: containerImage not pinned by hash: sdk/eventhub/event-hubs/test/stress/Dockerfile:4
Warn: containerImage not pinned by hash: sdk/identity/identity/integration/AzureKubernetes/Dockerfile:12
Warn: containerImage not pinned by hash: sdk/identity/identity/test/manual-integration/Kubernetes/Dockerfile:12
Warn: containerImage not pinned by hash: sdk/servicebus/service-bus/test/stress/Dockerfile:4
Warn: npmCommand not pinned by hash: sdk/eventhub/event-hubs/test/stress/Dockerfile:10
Warn: npmCommand not pinned by hash: sdk/identity/identity/integration/AzureKubernetes/Dockerfile:18
Warn: npmCommand not pinned by hash: sdk/identity/identity/test/manual-integration/Kubernetes/Dockerfile:17
Warn: npmCommand not pinned by hash: sdk/identity/identity/test/manual-integration/Kubernetes/Dockerfile:18
Warn: npmCommand not pinned by hash: sdk/servicebus/service-bus/test/stress/Dockerfile:10
Warn: npmCommand not pinned by hash: .devcontainer/init.sh:11
Warn: npmCommand not pinned by hash: .scripts/automation_init.sh:2
Warn: npmCommand not pinned by hash: .scripts/automation_init.sh:3
Warn: npmCommand not pinned by hash: .scripts/automation_init.sh:4
Info: 0 out of 3 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 2 third-party GitHubAction dependencies pinned
Info: 0 out of 9 npmCommand dependencies pinned
Info: 0 out of 4 containerImage dependencies pinned

0

Fuzzing

Determines if the project uses fuzzing.

Score

7.2

/10

Last Scanned on 2025-02-03

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

Other packages similar to @azure/logger

@azure/logger-js

1.3.2

Simple logger for JavaScript projects

@mcma/azure-logger

1.0.0

Add Azure AppInsights logging to your MCMA services

azure-table-logger

1.0.8

A logger using pino or winston that appending to Azure Data Table automatically

@dvsa/azure-logger

7.0.3

Shareable Logging Facade, implemented with Winston