@byu-oit-sdk/client-byu
A fetch client with automatic retries and oauth authorization
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is sibling first-party @byu-oit-sdk package, not third-party. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Trusted long-running publisher bot with strong approval track record. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 5 / 14 | |
| 0.11.0 | 5 / 14 | |
| 0.10.0 | 4 / 13 | |
| 0.9.2 | 4 / 14 | |
| 0.9.1 | 4 / 14 | |
| 0.9.0 | 4 / 14 | |
| 0.8.22 | 3 / 13 | |
| 0.8.21 | 3 / 13 | |
| 0.8.20 | 3 / 13 | |
| 0.8.19 | 3 / 13 | |
| 0.8.18 | 3 / 13 | |
| 0.8.17 | 3 / 13 | |
| 0.8.16 | 3 / 13 | |
| 0.8.15 | 3 / 13 | |
| 0.8.14 | 3 / 13 | |
| 0.8.13 | 3 / 13 | |
| 0.8.12 | 3 / 13 | |
| 0.8.11 | 3 / 13 | |
| 0.8.10 | 3 / 13 | |
| 0.8.9 | 3 / 13 | |
| 0.8.8 | 3 / 13 | |
| 0.8.7 | 7 / 13 | |
| 0.8.5 | 7 / 13 | |
| 0.8.4 | 7 / 13 | |
| 0.8.3 | 7 / 13 |
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.