
Research
/Security News
TensorLake npm SDK Compromised in ChainDrop Shai-Hulud Credential-Stealing Attack
Tensorlake npm SDK version 0.5.144 was compromised in a ChainDrop / Shai-Hulud attack, delivering credential-stealing malware.
@azure/arm-computeworkloadmanager
Advanced tools
This package contains an isomorphic SDK (runs both in Node.js and in browsers) for Azure WorkloadManager client.
Key links:
See our support policy for more details.
@azure/arm-computeworkloadmanager packageInstall the Azure WorkloadManager client library for JavaScript with npm:
npm install @azure/arm-computeworkloadmanager
WorkloadManagerClientTo create a client object to access the Azure WorkloadManager API, you will need the endpoint of your Azure WorkloadManager resource and a credential. The Azure WorkloadManager client can use Microsoft Entra credentials to authenticate.
You can find the endpoint for your Azure WorkloadManager resource in the Azure Portal.
You can authenticate with Microsoft Entra ID using a credential from the @azure/identity library or an existing Microsoft Entra token.
To use the DefaultAzureCredential provider shown below, or other credential providers provided with the Azure SDK, please install the @azure/identity package:
npm install @azure/identity
You will also need to register a new Microsoft Entra application and grant access to Azure WorkloadManager by assigning the suitable role to your service principal (note: roles such as "Owner" will not grant the necessary permissions).
For more information about how to create a Microsoft Entra application check out this guide.
Using Node.js and Node-like environments, you can use the DefaultAzureCredential class to authenticate the client.
import { WorkloadManagerClient } from "@azure/arm-computeworkloadmanager";
import { DefaultAzureCredential } from "@azure/identity";
const subscriptionId = "00000000-0000-0000-0000-000000000000";
const client = new WorkloadManagerClient(new DefaultAzureCredential(), subscriptionId);
For browser environments, use the InteractiveBrowserCredential from the @azure/identity package to authenticate.
import { InteractiveBrowserCredential } from "@azure/identity";
import { WorkloadManagerClient } from "@azure/arm-computeworkloadmanager";
const credential = new InteractiveBrowserCredential({
tenantId: "<YOUR_TENANT_ID>",
clientId: "<YOUR_CLIENT_ID>",
});
const subscriptionId = "00000000-0000-0000-0000-000000000000";
const client = new WorkloadManagerClient(credential, subscriptionId);
To use this client library in the browser, first you need to use a bundler. For details on how to do this, please refer to our bundling documentation.
WorkloadManagerClient is the primary interface for developers using the Azure WorkloadManager client library. Explore the methods on this client object to understand the different features of the Azure WorkloadManager service that you can access.
Enabling logging may help uncover useful information about failures. In order to see a log of HTTP requests and responses, set the AZURE_LOG_LEVEL environment variable to info. Alternatively, logging can be enabled at runtime by calling setLogLevel in the @azure/logger:
import { setLogLevel } from "@azure/logger";
setLogLevel("info");
For more detailed instructions on how to enable logs, you can look at the @azure/logger package docs.
Please take a look at the samples directory for detailed examples on how to use this library.
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.
FAQs
A generated SDK for WorkloadManagerClient.
The npm package @azure/arm-computeworkloadmanager receives a total of 177 weekly downloads. As such, @azure/arm-computeworkloadmanager popularity was classified as not popular.
We found that @azure/arm-computeworkloadmanager demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.

Research
/Security News
Tensorlake npm SDK version 0.5.144 was compromised in a ChainDrop / Shai-Hulud attack, delivering credential-stealing malware.

Research
/Security News
Socket found 16 malicious Firefox extensions designed to steal crypto wallet recovery phrases and private keys using cloned Rabby and OKX interfaces.

Product
Socket now scans VS Code extensions, giving teams early detection of risky behaviors, hidden capabilities, and supply chain threats in developer tools.