@azure/ms-rest-js — Greenflagged

Isomorphic client Runtime for Typescript/node.js/browser javascript client libraries generated using AutoRest

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

amarzaveryvladbarosanveronicaggazure-sdk

Keywords

isomorphicbrowserjavascriptnodemicrosoftautorestclientruntime

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Historical transition (2019) from individual Microsoft employee account (sergeyshandar) to official azure-sdk team account. Clearly a legitimate organizational handoff, not a compromise.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): tunnel and @types/tunnel are well-known, legitimate packages for HTTP proxy support — appropriate additions for an Azure REST client library.	ai	2026/04/24
semgrep	semgrep:base64-decode	AI (semgrep): Base64 decode is used for standard HTTP client functionality (e.g., Basic Auth). The code is a simple Buffer.from(value, 'base64') utility — no obfuscation or malicious payload handling.	ai	2026/04/24
phantom-deps	phantom-dep:@types/tunnel	AI (phantom-deps): @types/tunnel is a TypeScript type package listed as a runtime dep per Azure SDK convention; not directly imported as a module but provides type augmentation.	ai	2026/04/24
phantom-deps	phantom-dep:@types/node-fetch	AI (phantom-deps): @types/node-fetch is a TypeScript type package listed as a runtime dep per Azure SDK convention; not directly imported as a module but provides type augmentation.	ai	2026/04/24

Versions (showing 51 of 62)

View all versions

Version	Deps	Published
2.7.0	8 / 66	2023-07-06
2.6.6	9 / 67	2023-04-10
2.6.4	9 / 67	2022-11-28
2.6.2	9 / 65	2022-07-29
2.6.1	9 / 64	2022-03-01
2.6.0	9 / 63	2021-08-18
2.5.3	9 / 63	2021-07-12
2.5.2	9 / 63	2021-06-15
2.5.1	9 / 63	2021-06-10
2.5.0	9 / 63	2021-05-10
2.4.1	9 / 63	2021-05-05
2.4.0	9 / 63	2021-04-19
2.3.0	9 / 63	2021-03-29
2.2.3	11 / 61	2021-02-11
2.2.2	11 / 61	2021-02-09
2.2.1	11 / 60	2021-02-05
2.2.0	11 / 59	2021-01-26
2.1.0	10 / 59	2020-10-13
2.0.8	10 / 59	2020-07-24
2.0.7	10 / 59	2020-05-04
2.0.6	10 / 59	2020-04-23
2.0.5	10 / 60	2020-01-08
2.0.4	10 / 60	2019-07-31
2.0.3	10 / 60	2019-07-11
2.0.2	10 / 61	2019-07-09
2.0.1	10 / 61	2019-06-26
2.0.0	10 / 61	2019-06-24
1.11.2	8 / 60	2021-02-11
1.11.1	7 / 61	2021-02-11
1.11.0	7 / 61	2021-02-05
1.10.0	8 / 60	2021-02-02
1.9.1	8 / 59	2021-01-07
1.9.0	8 / 59	2020-10-13
1.8.15	8 / 59	2020-04-29
1.8.14	8 / 59	2019-12-10
1.8.13	8 / 59	2019-06-16
1.8.12	8 / 59	2019-06-07
1.8.11	8 / 59	2019-06-06
1.8.10	8 / 59	2019-06-05
1.8.8	8 / 59	2019-06-03
1.8.7	8 / 59	2019-05-16
1.8.6	8 / 59	2019-05-11
1.8.4	8 / 58	2019-05-07
1.8.2	8 / 58	2019-04-25
1.8.1	8 / 58	2019-04-01
1.8.0	8 / 58	2019-03-19
1.7.0	8 / 58	2019-02-11
1.6.0	8 / 58	2019-01-30
1.5.3	8 / 58	2019-01-26
1.5.0	6 / 56	2019-01-16
1.4.1	6 / 56	2019-01-15

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.6

1 finding

LOW No provenance attestation provenance

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

v2.6.4

1 finding

LOW No provenance attestation provenance

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

v2.6.2

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.3

1 finding

LOW No provenance attestation provenance

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

v2.5.2

1 finding

LOW No provenance attestation provenance

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

v2.5.1

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.3

1 finding

LOW No provenance attestation provenance

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

v2.2.2

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.11.2

1 finding

LOW No provenance attestation provenance

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

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

1 finding

LOW No provenance attestation provenance

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

v1.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.15

1 finding

LOW No provenance attestation provenance

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

v1.8.14

1 finding

LOW No provenance attestation provenance

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

v1.8.13

1 finding

LOW No provenance attestation provenance

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

v1.8.12

1 finding

LOW No provenance attestation provenance

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

v1.8.11

1 finding

LOW No provenance attestation provenance

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

v1.8.10

1 finding

LOW No provenance attestation provenance

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

v1.8.8

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sergeyshandar → azure-sdk (on 2019-06-03) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-03. This could indicate a legitimate maintainer transition or an account compromise.

v1.8.7

1 finding

LOW No provenance attestation provenance

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

v1.8.6

1 finding

LOW No provenance attestation provenance

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

v1.8.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: sergeyshandar → azure-sdk (on 2019-05-07) provenance

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

v1.8.2

2 findings

HIGH Publisher changed: sergeyshandar → azure-sdk (on 2019-04-25) provenance

This version was published by a different npm account than previous versions on 2019-04-25. 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.8.1

2 findings

HIGH Publisher changed: sergeyshandar → azure-sdk (on 2019-04-01) provenance

This version was published by a different npm account than previous versions on 2019-04-01. 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.8.0

2 findings

HIGH Publisher changed: sergeyshandar → azure-sdk (on 2019-03-19) provenance

This version was published by a different npm account than previous versions on 2019-03-19. 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.7.0

2 findings

HIGH Publisher changed: sergeyshandar → azure-sdk (on 2019-02-11) provenance

This version was published by a different npm account than previous versions on 2019-02-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.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.3

2 findings

HIGH Publisher changed: sergeyshandar → azure-sdk (on 2019-01-26) provenance

This version was published by a different npm account than previous versions on 2019-01-26. 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.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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