View azure-iot-device-http on Snyk Open Source Advisor

Package Health Score

58 / 100

security
Security review needed
popularity
Limited
maintenance
Inactive
community
Active

Explore Similar Packages

central
36

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
1.14.3	\|	07/2023	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.13.9	\|	04/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.12.3	\|	05/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.11.2	\|	01/2020		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.10.3	\|	09/2019		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Yes

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (455)

GitHub Stars: 261
Forks: 226
Contributors: 80

Direct Usage Popularity

The npm package azure-iot-device-http receives a total of 455 downloads a week. As such, we scored azure-iot-device-http popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package azure-iot-device-http, we found that it has been starred 261 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 80
Funding: No

With more than 10 contributors for the azure-iot-device-http repository, this is possibly a sign for a growing and inviting community.

Embed Package Health Score Badge

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 10
Open PR: 3
Last Release: 1 year ago
Last Commit: 1 year ago

Further analysis of the maintenance status of azure-iot-device-http based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for azure-iot-device-http is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >= 14.0.0

Age: 9 years
Dependencies: 6 Direct
Versions: 119
Install Size: 65.1 kB
Dist-tags: 14
# of Files: 10
Maintainers: 6
TS Typings: Yes

azure-iot-device-http has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use azure-iot-device-http?

To help you get started, we've collected the most common ways that azure-iot-device-http is being used within popular public projects.

Azure / azure-iot-sdk-node / device / samples / module_send_event.js View on Github

const run = async() => {
    try {
        console.log('Initializing Module Client.');
        const moduleClient = ModuleClient.fromConnectionString(process.env.DEVICE_CONNECTION_STRING, Mqtt);
        // We use the iot hub connection string to create the client rather than the actual event hub end point
        console.log('Initializing Event Hub Client.');
        const eventHubClient = await EventHubClient.createFromIotHubConnectionString(process.env.IOTHUB_CONNECTION_STRING); 
        console.log('Initializing HTTP Device Client.');
        const httpClient = HttpClientFromConnectionString(process.env.DEVICE_CONNECTION_STRING);
        console.log('Initialized clients!');

        console.log('Getting information from Event Hub.');
        const partitionIds = await eventHubClient.getPartitionIds(); //read more about partitions https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-features#partitions
        const startingPosition = EventPosition.fromEnqueuedTime(Date.now() - 1000); //subtracting a second to account for delay
        
        const eventLabel = 'beepBoop'; //label our events
        const sendDummyMessage = m => moduleClient.sendOutputEvent(eventLabel, m); //send helper

        console.log('Creating messages to send to via Module Client');
        //generate some messages
        const messageCount = 10;
        const importantMessages = [...Array(messageCount).keys()].map(generateImportantMessage);

        console.log('Sending messages via Module Client.');
        //iterative send approach

View more ways to use azure-iot-device-http

#azure-iot-device-http Communicate with Azure IoT Hub from any device over HTTP 1.1.

Install

npm install -g azure-iot-device-http@latest to get the latest (pre-release) version.

Getting Started

Create a device client:

var clientFromConnectionString = require('azure-iot-device-http').clientFromConnectionString;
var Message = require('azure-iot-device').Message;

var connectionString = '[IoT Hub device connection string]';

var client = clientFromConnectionString(connectionString);

Create a callback that sends a message and receives messages. When it receives a message it sends an acknowledgement receipt to the server:

var connectCallback = function (err) {
  if (err) {
    console.error('Could not connect: ' + err);
  } else {
    console.log('Client connected');
    var message = new Message('some data from my device');
    client.sendEvent(message, function (err) {
      if (err) console.log(err.toString());
    });

    client.on('message', function (msg) { 
      console.log(msg); 
      client.complete(msg, function () {
        console.log('completed');
      });
    }); 
  }
};

Open the connection and invoke the callback:

client.open(connectCallback);

azure-iot-device-http dependencies

async azure-iot-common azure-iot-device azure-iot-http-base debug node-crontab

azure-iot-device-http development dependencies

@types/node azure-iothub eslint @typescript-eslint/eslint-plugin @typescript-eslint/eslint-plugin-tslint @typescript-eslint/parser eslint-plugin-jsdoc eslint-plugin-mocha eslint-plugin-no-null eslint-plugin-no-only-tests eslint-plugin-promise eslint-plugin-security chai mocha nyc sinon source-map-support typescript

FAQs

What is azure-iot-device-http?

HTTP transport for Azure IoT device SDK. Visit Snyk Advisor to see a full health score report for azure-iot-device-http, including popularity, security, maintenance & community analysis.

Is azure-iot-device-http popular?

The npm package azure-iot-device-http receives a total of 455 weekly downloads. As such, azure-iot-device-http popularity was classified as limited. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is azure-iot-device-http well maintained?

We found indications that azure-iot-device-http is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is azure-iot-device-http safe to use?

While scanning the latest version of azure-iot-device-http, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 12 December-2024, at 13:39 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

azure-iot-device-http

HTTP transport for Azure IoT device SDK For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (455)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use azure-iot-device-http?

Install

Getting Started

azure-iot-device-http dependencies

azure-iot-device-http development dependencies

FAQs

What is azure-iot-device-http?

Is azure-iot-device-http popular?

Is azure-iot-device-http well maintained?

Is azure-iot-device-http safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (455)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use azure-iot-device-http?

Install

Getting Started

azure-iot-device-http dependencies

azure-iot-device-http development dependencies

FAQs

What is azure-iot-device-http?

Is azure-iot-device-http popular?

Is azure-iot-device-http well maintained?

Is azure-iot-device-http safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues