@byu-oit-sdk/client-identities
BYU Identities v2 API
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): SDK package for BYU OIT; README links are API documentation references, not a phishing link farm. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 5 / 13 | |
| 0.12.0 | 5 / 13 | |
| 0.11.0 | 5 / 12 | |
| 0.10.6 | 5 / 12 |
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.