adal-node
Windows Azure Active Directory Client Library for node
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is a framework-scoped TypeScript type package; convention-loaded and stable for this package. | ai | |
| source-diff | encoded-string-file:test/username-password.js | AI (source-diff): Long strings are base64-encoded JWT test fixtures in test files, not obfuscated payloads. Stable for this package. | ai | |
| dependencies | unvetted-dep:request | AI (dependencies): request is a well-known, widely-used HTTP client package; its presence in adal-node is expected and not a security concern. | ai | |
| dependencies | unvetted-dep:xmldom | AI (dependencies): xmldom is a standard XML parser; its use in an OAuth/ADAL library is expected and not a security concern for this package. | ai | |
| license | uncommon-license:Apache 2.0 | AI (license): Apache 2.0 is a standard permissive license; the finding is a false positive due to non-canonical string formatting. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.2.4 | 8 / 10 | |
| 0.1.26 | 9 / 9 | |
| 0.1.23 | 8 / 4 | |
| 0.1.20 | 8 / 4 | |
| 0.1.17 | 8 / 4 | |
| 0.1.16 | 8 / 4 | |
| 0.1.5 | 6 / 5 |
v0.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
2 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.