npm access token
ID npm_access_token
DatatypeNot PIIidentifierDraft
This record is a draft: it has not been reviewed yet and may be incomplete or wrong. Do not rely on it for compliance decisions. Help improve it (see CONTRIBUTING.md).
Access token of the npm package registry in the format introduced in 2021: the prefix npm_ followed by 36 letters and digits, the last six of which are a Base62-encoded CRC32 checksum. Older npm tokens are bare UUIDs.
- Parent datatype
- Access token
access_token - Categories
- Secrets and credentials (passwords, keys, tokens)
- Countries
- Global (not tied to a country)
- Languages
- Common to most languages
- Quality
- 78/100 · missing: second example, mapping (Wikidata, Schema.org, ...), translation
- Metacrafter rules
- no detection rule yet
- Supported by tools
- detect-secrets, Gitleaks, Semgrep, TruffleHog
Regular expression
^npm_[A-Za-z0-9]{36}$Python re syntax.
Examples
| Value | Description |
|---|---|
| npm_ExampleTokenExampleTokenExampleToken | Constructed, non-functional value |
| npm_ExampleTokenExampleTokenExampl invalid | Too short |
Sources
- doc: https://github.blog/changelog/2021-09-23-npm-has-a-new-access-token-format/
- other: https://github.com/gitleaks/gitleaks/blob/master/config/gitleaks.toml
Use this record
- Page URL:
http://registry.apicrafter.io/datatype/npm_access_token - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/secrets/npm_access_token.yamlon GitHub