go-tokenless
NPM · GO-TOKENLESS
Move npm publishing in GitHub Actions from NPM_TOKEN to trusted publishing (OIDC).
Available components
Last scanned (17 hours ago)
Scores higher than 65% of npm servers
Category CI/CD and DevOps
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Continuous-Actions/go-tokenless). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 407 tokens (~203/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Analysed npm/go-tokenless@1.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Continuous-Actions/go-tokenless |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Continuous-Actions/go-tokenless/.github/workflows/release.yml@refs/tags/v1.1.0 |
| Rekor log index | 3109236959 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ff9727e1e573721908d73973c402a0489bb7bfb634b68459d5554e9e48979a1fe87db009fb76a5a0520073b9caed37fef2a53839ccd8f0daf6350584d |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_trusted_publishing Apply npm trusted publishing migration ~198
Writes the workflow and package.json changes from plan_trusted_publishing to disk (no git commit, no network writes). Returns the plan with status "applied" and the steps the user must still do with npm 2FA (npm trust commands, deleting the NPM_TOKEN secret).
| Name | Type | Req | Description |
|---|---|---|---|
| npmArgs | string | – | Extra arguments appended to the npm commands it generates. |
| npmVersion | string | – | npm version range for the inserted upgrade step. Default ^12; other versions may break publishing. |
| offline | boolean | – | Skip npm registry lookups. |
| path | string | yes | Absolute path to the repository root. |
| readToken | string | – | Secret name (e.g. NPM_READ_TOKEN) of a read-only npm token to give install steps, for private org packages. Publish steps stay tokenless. |
| repo | string | – | GitHub owner/repo, if the git remote is not "origin". |
No output schema declared.
No examples provided.
plan_trusted_publishing Plan npm trusted publishing migration ~209
Read-only. Finds GitHub Actions workflows that publish to npm with a token (NPM_TOKEN / NODE_AUTH_TOKEN) and returns the exact changes needed to switch to npm trusted publishing (OIDC): workflow diff, package.json repository fixes, `npm trust github` commands, and the remaining human steps. Use before apply_trusted_publishing.
| Name | Type | Req | Description |
|---|---|---|---|
| npmArgs | string | – | Extra arguments appended to the npm commands it generates. |
| npmVersion | string | – | npm version range for the inserted upgrade step. Default ^12; other versions may break publishing. |
| offline | boolean | – | Skip npm registry lookups. |
| path | string | yes | Absolute path to the repository root. |
| readToken | string | – | Secret name (e.g. NPM_READ_TOKEN) of a read-only npm token to give install steps, for private org packages. Publish steps stay tokenless. |
| repo | string | – | GitHub owner/repo, if the git remote is not "origin". |
No output schema declared.
No examples provided.
How do I install the go-tokenless MCP server?
go-tokenless runs locally as an npm package, launched with npx -y go-tokenless. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · go-tokenless
claude mcp add continuous-actions-go-tokenless -- npx -y go-tokenless
What is the go-tokenless MCP server?
go-tokenless is an MCP server listed in the public MCP registry as io.github.Continuous-Actions/go-tokenless. Move npm publishing in GitHub Actions from NPM_TOKEN to trusted publishing (OIDC). This page covers its npm package (go-tokenless).
Is the go-tokenless MCP server safe to use?
go-tokenless scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the go-tokenless MCP server expose?
go-tokenless exposes 2 tools: plan_trusted_publishing, apply_trusted_publishing. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.
Is the go-tokenless MCP server still maintained?
go-tokenless is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the go-tokenless MCP server under?
go-tokenless declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.