@microsoft/microsoft-graph-client No license 8 versions

@microsoft/microsoft-graph-client

npm Repository Homepage

8

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

microsoft1esnikithaucmicrosoftgraph

Keywords

MicrosoftGraphSDKJavaScriptClient

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	dormant-publish	AI (publish-pattern): Established SDK with periodic release cadence, not account takeover pattern.	ai	2026/07/25
provenance	missing-githead	AI (provenance): Metadata gap only; no behavioral change, trusted publisher.	ai	2026/07/25
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): Framework-scoped runtime helper loaded by convention.	ai	2026/07/25

Versions (showing 8 of 8)

Version	Deps	Published
3.0.7	2 / 44	2023-09-19
3.0.6	2 / 44	2023-08-24
3.0.5	2 / 44	2023-01-31
3.0.4	2 / 45	2022-11-10
3.0.3	2 / 45	2022-11-03
3.0.2	2 / 44	2022-02-09
3.0.1	2 / 44	2021-11-15
3.0.0	2 / 44	2021-08-09

v3.0.6

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoftgraph.

LOW No provenance attestation provenance

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

v3.0.5

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoftgraph.

LOW No provenance attestation provenance

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

v3.0.4

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoftgraph.

LOW No provenance attestation provenance

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

v3.0.3

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: microsoftgraph.

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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