@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, so a manually published version cannot be tied back to a reviewed commit.
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 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 5 / 13 | |
| 0.12.0 | 5 / 13 | |
| 0.11.0 | 5 / 12 | |
| 0.10.6 | 5 / 12 | |
| 0.10.5 | 5 / 12 | |
| 0.10.4 | 5 / 12 | |
| 0.10.3 | 5 / 12 | |
| 0.10.2 | 5 / 12 | |
| 0.10.1 | 5 / 12 | |
| 0.10.0 | 5 / 12 | |
| 0.9.20 | 5 / 12 | |
| 0.9.19 | 5 / 12 | |
| 0.9.18 | 5 / 12 | |
| 0.9.17 | 7 / 12 | |
| 0.9.16 | 7 / 12 | |
| 0.9.15 | 7 / 12 | |
| 0.9.14 | 7 / 12 | |
| 0.9.11 | 7 / 12 | |
| 0.9.10 | 8 / 12 | |
| 0.9.9 | 8 / 12 | |
| 0.9.8 | 8 / 12 | |
| 0.9.7 | 8 / 12 | |
| 0.9.5 | 8 / 12 | |
| 0.9.4 | 8 / 12 | |
| 0.9.3 | 8 / 12 |
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.