@things-factory/auth-azure-ad
Module for Supporting User Authentication with Azure AD
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:passport-azure-ad | AI (dependencies): passport-azure-ad is a well-known Microsoft-maintained library; unvetted status is a registry gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@things-factory/auth-base | AI (dependencies): First-party monorepo dependency from the same hatiolab org; stable across all versions of this package. | ai | |
| dependencies | unvetted-dep:@things-factory/shell | AI (dependencies): First-party monorepo dependency from the same hatiolab org; stable across all versions of this package. | ai | |
| provenance | no-provenance | AI (provenance): Established @things-factory ecosystem package; lack of provenance is consistent across all prior versions. | ai | |
| phantom-deps | phantom-dep:passport | AI (phantom-deps): passport is a declared dep used via config/middleware patterns, not direct import; stable false positive for this auth package. | ai | |
| phantom-deps | phantom-dep:@operato/graphql | AI (phantom-deps): Referenced in config files as documented; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@operato/shell | AI (phantom-deps): Referenced in config files as documented; stable false positive for this monorepo package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 9.2.24 | 6 / 0 | |
| 9.2.17 | 6 / 0 | |
| 9.2.16 | 6 / 0 | |
| 9.2.13 | 6 / 0 | |
| 9.2.5 | 6 / 0 | |
| 9.1.19 | 6 / 0 | |
| 9.0.41 | 6 / 0 | |
| 9.0.34 | 6 / 0 | |
| 9.0.25 | 6 / 0 | |
| 9.0.20 | 6 / 0 | |
| 9.0.2 | 6 / 0 | |
| 9.0.0 | 6 / 0 | |
| 8.0.88 | 6 / 0 | |
| 8.0.87 | 6 / 0 | |
| 8.0.86 | 6 / 0 | |
| 8.0.75 | 6 / 0 | |
| 8.0.74 | 6 / 0 | |
| 8.0.64 | 6 / 0 | |
| 8.0.63 | 6 / 0 | |
| 6.4.10 | 6 / 0 | |
| 6.4.8 | 6 / 0 |
v9.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.4.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (heartyoh) than the most recent previously approved version (nalshya113) on 2026-03-29, but heartyoh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.