Crowd.dev · OAuth Scopes

Crowd.dev OAuth Scopes

OAuth 2.0 searched

Crowd.dev publishes 17 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Crowd.dev API on a user’s behalf.

Tokens are issued from https://linuxfoundation.auth0.com/oauth/token.

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.

CompanyCommunityDeveloper RelationsDeveloper Data PlatformIdentity ResolutionOpen-SourceCommunity Data PlatformOpen Source Intelligence
Scopes: 17 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://linuxfoundation.auth0.com/oauth/token
Flows
clientCredentials

Scopes (17)

ScopeDescriptionFlows
read:akrites-packages Read package detail on the /akrites-external route (Akrites-namespaced target scope) clientCredentials
read:akrites-advisories Read package security advisories on the /akrites-external route (Akrites-namespaced target scope) clientCredentials
read:akrites-maintainers Read package security contacts on the /akrites-external route (Akrites-namespaced target scope) clientCredentials
read:maintainer-roles Read security contacts (interim scope for Contacts; see the Contacts tag) clientCredentials
read:member-identities Read member identities clientCredentials
read:members Read member profiles clientCredentials
read:organizations Look up organizations clientCredentials
read:packages Read package detail clientCredentials
read:project-affiliations Read project affiliations clientCredentials
read:stewardships Read package stewardship data clientCredentials
read:work-experiences Read work experiences clientCredentials
write:member-identities Create and verify member identities clientCredentials
write:members Create member profiles clientCredentials
write:organizations Create organizations clientCredentials
write:project-affiliations Override project affiliations clientCredentials
write:work-experiences Create, update, verify, and delete work experiences clientCredentials
write:stewardships Open, assign, escalate and update OSSPREY Program admin stewardship actions clientCredentials

Source

OAuth Scopes

Raw ↑
generated: '2026-08-14'
method: searched
source: https://github.com/linuxfoundation/crowd.dev/blob/main/docs/adr/0016-akrites-cdp-public-api-authentication.md
docs: https://github.com/linuxfoundation/crowd.dev/blob/main/docs/adr/0016-akrites-cdp-public-api-authentication.md
derived_from: openapi/crowddev-cdp-akrites-external-openapi.yml, openapi/crowddev-cdp-public-openapi.yml
note: >-
  Upgraded from derived to searched on 2026-08-14. ADR-0016 documents a scope migration the
  OpenAPI does not yet reflect: three Akrites-namespaced scopes are now defined on the
  `cdp_public_api` Auth0 API and granted only to the `Akrites Enclave` client, while each
  /akrites-external subrouter transitionally accepts EITHER the namespaced scope OR its legacy
  Self Serve equivalent via `requireScopes([...], 'any')`. The legacy fallbacks are removed once
  Akrites confirms end-to-end token exchange. The specs in openapi/ still declare only the legacy
  names, so both sets are recorded below with their status.
auth0_api: cdp_public_api
schemes:
- name: M2MBearer
  source: openapi/crowddev-cdp-akrites-external-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://linuxfoundation.auth0.com/oauth/token
  description: 'Auth0 machine-to-machine client-credentials flow. Akrites exchanges its client
    ID/secret with Auth0 for a JWT and sends it as `Authorization: Bearer <token>`; CDP only
    verifies the resulting token.'
- name: OAuth2Bearer
  source: openapi/crowddev-cdp-public-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://linuxfoundation.auth0.com/oauth/token
  description: 'OAuth 2.0 client credentials flow via Auth0. The consuming service obtains a
    JWT using its client ID and secret, then passes it as `Authorization: Bearer <token>`'
scopes:
- scope: read:akrites-packages
  description: Read package detail on the /akrites-external route (Akrites-namespaced target scope)
  flows:
  - clientCredentials
  status: target
  granted_to: Akrites Enclave
  sources:
  - https://github.com/linuxfoundation/crowd.dev/blob/main/docs/adr/0016-akrites-cdp-public-api-authentication.md
  note: >-
    Defined on cdp_public_api and granted only to the Akrites Enclave client. Not yet declared in
    openapi/crowddev-cdp-akrites-external-openapi.yml, which still lists the legacy read:packages.
- scope: read:akrites-advisories
  description: Read package security advisories on the /akrites-external route (Akrites-namespaced target scope)
  flows:
  - clientCredentials
  status: target
  granted_to: Akrites Enclave
  sources:
  - https://github.com/linuxfoundation/crowd.dev/blob/main/docs/adr/0016-akrites-cdp-public-api-authentication.md
  note: >-
    The akrites-external spec still notes the final name was undecided (read:advisories vs
    cdp:advisories:read); ADR-0016 settles it as read:akrites-advisories.
- scope: read:akrites-maintainers
  description: Read package security contacts on the /akrites-external route (Akrites-namespaced target scope)
  flows:
  - clientCredentials
  status: target
  granted_to: Akrites Enclave
  sources:
  - https://github.com/linuxfoundation/crowd.dev/blob/main/docs/adr/0016-akrites-cdp-public-api-authentication.md
  note: >-
    Gates security-contact PII. Legacy fallback during cut-over is read:maintainer-roles, never
    read:packages.
- scope: read:maintainer-roles
  status: legacy
  description: Read security contacts (interim scope for Contacts; see the Contacts tag)
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-akrites-external-openapi.yml
  - openapi/crowddev-cdp-public-openapi.yml
- scope: read:member-identities
  description: Read member identities
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: read:members
  description: Read member profiles
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: read:organizations
  description: Look up organizations
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: read:packages
  description: Read package detail
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-akrites-external-openapi.yml
- scope: read:project-affiliations
  description: Read project affiliations
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: read:stewardships
  description: Read package stewardship data
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-akrites-external-openapi.yml
- scope: read:work-experiences
  description: Read work experiences
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: write:member-identities
  description: Create and verify member identities
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: write:members
  description: Create member profiles
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: write:organizations
  description: Create organizations
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: write:project-affiliations
  description: Override project affiliations
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: write:work-experiences
  description: Create, update, verify, and delete work experiences
  flows:
  - clientCredentials
  sources:
  - openapi/crowddev-cdp-public-openapi.yml
- scope: write:stewardships
  description: Open, assign, escalate and update OSSPREY Program admin stewardship actions
  flows:
  - clientCredentials
  status: declared-not-enforced
  sources:
  - openapi/crowddev-cdp-stewardships-openapi.yml
  note: >-
    Declared as required on all four stewardship write operations, but the spec's own V1 note says
    the scope "is not yet added to the Auth0 staging tenant - scope enforcement is temporarily
    disabled. See CM-1235." Recorded as declared, not as enforced.

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/crowddev-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 email required.

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