@maxim_mazurok/gapi.client.admin-datatransfer_v1
TypeScript typings for Admin SDK API datatransfer_v1
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Auto-generated Google API typings; README link-dump and no keywords are expected for this package family. | ai | |
| dependencies | unvetted-dep:@types/gapi.client.discovery-v1 | AI (dependencies): Pure @types declaration dependency; no runtime code, stable pattern across all versions of this typings package. | ai | |
| phantom-deps | phantom-dep:@types/gapi.client | AI (phantom-deps): Type-only dependency loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@types/gapi.client.discovery-v1 | AI (phantom-deps): Type-only dependency loaded by convention; not directly imported by design. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 0.3.20260602 | 2 / 0 | |
| 0.3.20260531 | 2 / 0 | |
| 0.3.20260522 | 2 / 0 | |
| 0.3.20260519 | 2 / 0 | |
| 0.3.20260513 | 2 / 0 | |
| 0.3.20260511 | 2 / 0 | |
| 0.3.20260505 | 2 / 0 | |
| 0.3.20260504 | 2 / 0 | |
| 0.3.20260421 | 2 / 0 | |
| 0.3.20260413 | 2 / 0 | |
| 0.2.20260401 | 2 / 0 | |
| 0.2.20260324 | 2 / 0 | |
| 0.2.20260317 | 2 / 0 | |
| 0.2.20260316 | 2 / 0 | |
| 0.1.20260316 | 2 / 0 | |
| 0.1.20260227 | 2 / 0 | |
| 0.1.20260219 | 2 / 0 | |
| 0.1.20260217 | 2 / 0 | |
| 0.1.20260210 | 2 / 0 | |
| 0.1.20260120 | 2 / 0 | |
| 0.1.20260113 | 2 / 0 | |
| 0.1.20251216 | 2 / 0 | |
| 0.1.20251202 | 2 / 0 | |
| 0.1.20251120 | 2 / 0 | |
| 0.1.20251107 | 2 / 0 | |
| 0.1.20251006 | 2 / 0 | |
| 0.1.20250930 | 2 / 0 | |
| 0.1.20250916 | 2 / 0 | |
| 0.1.20250822 | 2 / 0 | |
| 0.0.20250813 | 2 / 0 | |
| 0.0.20250808 | 2 / 0 | |
| 0.0.20250804 | 2 / 0 | |
| 0.0.20250714 | 2 / 0 | |
| 0.0.20250707 | 2 / 0 | |
| 0.0.20250626 | 2 / 0 | |
| 0.0.20250623 | 2 / 0 | |
| 0.0.20250619 | 2 / 0 | |
| 0.0.20250616 | 2 / 0 | |
| 0.0.20250606 | 2 / 0 | |
| 0.0.20250527 | 2 / 0 | |
| 0.0.20250505 | 2 / 0 |
v0.3.20260602
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260531
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260522
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260519
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260513
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260511
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260505
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260504
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.20260413
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.20260401
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.20260324
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.20260317
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.20260316
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20260316
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20260227
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20260219
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20260217
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20260210
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20260120
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20260113
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20251216
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20251202
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20251120
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20251107
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20251006
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20250930
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20250916
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.20250822
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.20250813
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250808
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250804
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250714
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250707
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250626
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250623
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250619
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250616
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250606
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250527
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20250505
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.