Googleworkspace Cli

Google Workspace CLI — one command-line tool for Drive, Gmail, Calendar, Sheets, Docs, Chat, Admin, and more. Dynamically built from Google Discovery Service. Includes AI agent skills.

Agent Skills Rust Listed Apache-2.0

Is Googleworkspace Cli safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.3 / 10
Provenance None
Signed commits 89%
Last push 7d ago
Compare Googleworkspace Cli
Suggest a correction

In detail: Googleworkspace Cli scores 54.7/100 (Grade C), ranked #186 of 384 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 89% of recent commits are signed; last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Googleworkspace Cli could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Googleworkspace Cli and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/googleworkspace/cli, Apache-2.0, last pushed 2026-11-03. 89% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protection3
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 3
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 9
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages None

    No registry package. Googleworkspace Cli is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 4.2/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Googleworkspace Cli’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Googleworkspace Cli compares in Agent Skills

  1. #184 The Architect 54.8 +0.1
  2. #185 AI company 54.8 +0.1
  3. #186 Googleworkspace Cli 54.7 this agent
  4. #187 Ring 54.6 −0.1
  5. #188 Distilly 54.6 −0.1

Bars show each HVTrust score; the tick marks Googleworkspace Cli’s 54.7.

Where the 54.7 comes from

HVTrust dimensions vs the Agent Skills average

54.7 / 100 · 100.0% confidence

Googleworkspace Cli Agent Skills average (384 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.8 / 25
1.6 above avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.1 / 20
1.9 below avg 14.0
AdoptionLog-scaled stars · package downloads
10.8 / 20
1.7 above avg 9.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-26
Rank Moved
Rank rose 19 spots (#212 → #193)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View Agent Skills Report missing data
70.1
Activity sub-score · out of 100
#186

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 7 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
32.2k
Forks
2.0k
Last Push
2026-11-03
7 days ago
Commits (4 wk)
1?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
134
Rank Change
=
was #186

Analysis

Activity Inputs

70.1 / 100
StarsRepository reach
27.0 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
15.3 / 20

Common questions about Googleworkspace Cli

Public trust evidence for Googleworkspace Cli is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Googleworkspace Cli publish package provenance?
No published build provenance is currently detected for Googleworkspace Cli. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Googleworkspace Cli have an OpenSSF Scorecard?
Googleworkspace Cli has an OpenSSF Scorecard score of 4.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Googleworkspace Cli actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does Googleworkspace Cli use?
Googleworkspace Cli ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Googleworkspace Cli's commits signed?
89% of the last 100 commits to Googleworkspace Cli are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Googleworkspace Cli's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini

Maintain Googleworkspace Cli?

For maintainers

HVTrust scores Googleworkspace Cli from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 12HVTrust 2Grade 2Scorecard 1Delisted 1Listed 1Surface 1
2026-10-26
Rank Moved
Rank rose 19 spots (#212 → #193)
2026-09-25
Rank Moved
Rank dropped 15 spots (#159 → #174)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Google Gemini
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 35 spots (#125 → #160)
2026-09-23
HVTrust Changed
HVTrust up 12.2pts (42.2 → 54.4)
2026-09-22
Newly Listed
First tracked at rank #125
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank dropped 10 spots (#136 → #146)
2026-09-05
Scorecard Added
OSSF Scorecard: 4.2/10
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 175 spots (#306 → #131)
2026-09-05
HVTrust Changed
HVTrust up 32.4pts (22.0 → 54.4)
2026-09-01
Rank Moved
Rank dropped 10 spots (#273 → #283)
2026-08-30
Rank Moved
Rank dropped 20 spots (#244 → #264)
2026-08-29
Rank Moved
Rank dropped 27 spots (#217 → #244)
2026-08-28
Rank Moved
Rank dropped 15 spots (#202 → #217)
2026-08-27
Rank Moved
Rank dropped 14 spots (#188 → #202)
2026-08-26
Rank Moved
Rank dropped 88 spots (#100 → #188)
2026-08-16
Rank Moved
Rank dropped 10 spots (#96 → #106)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/googleworkspace-cli.svg)](https://hvtracker.net/agents/googleworkspace-cli)
HTML:
<a href="https://hvtracker.net/agents/googleworkspace-cli"><img src="https://hvtracker.net/badge/googleworkspace-cli.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON