CHAOSS · OAuth Scopes

CHAOSS OAuth Scopes

OAuth 2.0 searched

CHAOSS uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

AnalyticsCommunity HealthDEILinux FoundationMetricsObservabilityOpen-SourceRiskSustainability
Scopes: 0 Flows: Method: searched

Scopes (0)

CHAOSS implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

📄 Provider scope reference: https://docs.collectoss.org/en/latest/login.html

Source

OAuth Scopes

Raw ↑ 
specification: API Commons OAuth Scopes
specificationVersion: '0.1'
provider: CHAOSS
providerId: chaoss
api: CollectOSS REST API
generated: '2026-09-05'
modified: '2026-09-05'
method: searched
source: >-
  https://docs.collectoss.org/en/latest/login.html and the published contract
  openapi/chaoss-collectoss-openapi.yml, both read 2026-09-05.
docs: https://docs.collectoss.org/en/latest/login.html
description: >-
  CollectOSS runs OAuth 2.0 authorization code but publishes NO scope vocabulary. This is a recorded
  absence, not an unfinished probe.
scope_count: 0
scopes: []
findings:
  - >-
    The OpenAPI declares no components.securitySchemes, so there is no `scopes` map to derive from.
    derive-oauth-scopes.py returned "with oauth2: 0" against this repo for exactly that reason.
  - >-
    The authorization page is documented as showing the user "what information will be shared", but
    no scope names, no permission reference page, and no per-operation scope requirements are
    published anywhere in the CollectOSS documentation.
  - >-
    Consequence for an integrator: authorization is all-or-nothing per Client Application. An agent
    cannot request least privilege because there is no privilege vocabulary to request from.
maintainers:
  - FN: Kin Lane
    email: info@apievangelist.com

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/chaoss-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.