@azure/msal-node-runtime
4
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
azureadneagrawamanrath
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Sparse README/keywords are typical for SDK sub-packages from large orgs; not indicative of spam. | ai | |
| install-scripts | install-script:install | AI (install-scripts): copyBinaries.js is a standard binary-copy step for this native broker package; stable across versions. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): Bundled platform-specific DLLs and .node files are the core deliverable of this native broker add-on; expected and stable. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.20.6 | 0 / 10 | |
| 0.20.5 | 0 / 10 | |
| 0.20.4 | 0 / 10 | |
| 0.0.1 | 0 / 10 |
v0.20.6
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.