@sebspark/openapi-client
A typed REST client for the definitions from openapi-typegen
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sebspark/otel | AI (dependencies): First-party sibling dep from same org monorepo; expected pattern for this package. | ai | |
| dependencies | unvetted-dep:@sebspark/retry | AI (dependencies): First-party sibling dep from same org monorepo; expected pattern for this package. | ai | |
| dependencies | unvetted-dep:@sebspark/openapi-core | AI (dependencies): First-party sibling dep from same org monorepo; expected pattern for this package. | ai | |
| dependencies | unvetted-dep:axios-auth-refresh | AI (dependencies): Well-known axios plugin for auth token refresh; stable third-party dep with no known advisories. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.2.10 | 5 / 3 | |
| 4.2.9 | 5 / 3 | |
| 4.2.8 | 5 / 3 | |
| 4.2.7 | 5 / 3 | |
| 4.2.6 | 5 / 3 | |
| 4.2.5 | 5 / 3 | |
| 4.2.4 | 5 / 3 | |
| 4.2.3 | 5 / 3 | |
| 4.2.2 | 5 / 3 | |
| 4.1.25 | 5 / 3 | |
| 4.1.2 | 4 / 6 | |
| 4.1.1 | 5 / 6 | |
| 4.1.0 | 6 / 6 | |
| 4.0.13 | 6 / 6 | |
| 4.0.12 | 6 / 6 | |
| 4.0.11 | 6 / 6 | |
| 4.0.9 | 6 / 6 | |
| 4.0.8 | 6 / 6 | |
| 4.0.7 | 6 / 7 | |
| 4.0.6 | 6 / 7 | |
| 4.0.5 | 6 / 7 | |
| 4.0.4 | 6 / 7 | |
| 4.0.3 | 6 / 7 | |
| 4.0.2 | 6 / 7 | |
| 4.0.1 | 6 / 7 | |
| 4.0.0 | 5 / 7 |
v4.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.