← Home

@azure/identity-broker

npm Repository Homepage
7
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

azure-sdkmicrosoft1esmicrosoft-oss-releases

Keywords

azurecloudentra-idWAMMSA support

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a standard TypeScript runtime helper; implicit dependency pattern is stable for Azure SDK packages. ai
phantom-deps phantom-dep:@azure/core-auth AI (phantom-deps): Framework-scoped Azure SDK package loaded by convention; stable false positive for this package. ai
phantom-deps phantom-dep:@azure/msal-node AI (phantom-deps): First-party Microsoft MSAL package; loaded by convention in broker auth flow, stable false positive. ai

Versions (showing 7 of 7)

Version Deps Published
1.4.0 5 / 18
1.3.0 5 / 19
1.2.1 5 / 14
1.2.0 5 / 16
1.1.0 5 / 20
1.0.1 5 / 19
1.0.0 5 / 22

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.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.

v1.0.1

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.

v1.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.