@byu-oit-sdk/client-persons
BYU Persons v3 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): Internal BYU OIT SDK package; README style and missing keywords are org conventions, not spam indicators. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.16.0 | 5 / 13 | |
| 0.15.0 | 5 / 13 | |
| 0.14.0 | 4 / 12 | |
| 0.13.6 | 4 / 12 | |
| 0.13.5 | 4 / 12 | |
| 0.13.4 | 4 / 12 | |
| 0.13.3 | 4 / 12 | |
| 0.13.2 | 4 / 12 | |
| 0.13.1 | 4 / 12 | |
| 0.13.0 | 4 / 12 | |
| 0.12.16 | 4 / 12 | |
| 0.12.15 | 4 / 12 | |
| 0.12.14 | 4 / 12 | |
| 0.12.13 | 6 / 12 | |
| 0.12.12 | 6 / 12 | |
| 0.12.11 | 6 / 12 | |
| 0.12.10 | 6 / 12 | |
| 0.12.7 | 6 / 12 | |
| 0.12.6 | 7 / 12 | |
| 0.12.5 | 7 / 12 | |
| 0.12.4 | 7 / 12 | |
| 0.12.3 | 7 / 12 | |
| 0.12.1 | 7 / 12 | |
| 0.12.0 | 7 / 12 | |
| 0.11.4 | 7 / 12 | |
| 0.11.3 | 7 / 12 |
v0.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.