← Home

@azure/ms-rest-azure-env

npm Repository Homepage

Isomorphic library that provides Azure endpoints for different Azure Environments/Clouds.

4
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

amarzaveryazure-sdkbillytrendsergeyshandarveronicaggvladbarosan

Keywords

nodeisomorphicazureenvironmentendpoint

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from sergeyshandar to azure-sdk reflects Microsoft's documented consolidation of Azure SDK packages under the official azure-sdk npm org account. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): azure-sdk maintainer addition is part of Microsoft's Azure SDK org consolidation, not a suspicious takeover. Stable for this package. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance attestation; no provenance is expected for packages published in 2019 by the azure-sdk org. ai

Versions (showing 4 of 4)

Version Deps Published
2.0.0 0 / 11
1.1.2 0 / 11
1.1.1 0 / 11
1.1.0 0 / 10

v2.0.0

2 findings
HIGH Publisher changed: sergeyshandar → azure-sdk (on 2019-07-11) provenance

This version was published by a different npm account than previous versions on 2019-07-11. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.