GitHub

security.token

A bad or expired token, secret or signature was presented

Profile

Logs

Written with

log()

Level

warn
View as Markdown

Security intents

Example

TS
log('security.token', 'Preview secret did not match', { ip: '203.0.113.7' });
Writes
TS
{
  "intent": "security.token",
  "level": "warn",
  "alert": false,
  "message": "Preview secret did not match",
  "data": {
    "ip": "203.0.113.7"
  },
  "time": "2026-10-09T12:00:00.000Z"
}

Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

  • If it is

    Use

  • A bad or expired token, secret or signature was presented

    security.token this page

Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

For registry authors

Starter intents. These are the intents prongs add logs puts in your registry. Change levels through the level.* intents, and point log() at your logger.

The entry prongs add logs writes into your registry. Change the level through its level.* ref.

TS
'security.token': {
  kind: 'semantic',
  description: 'A bad or expired token, secret or signature was presented',
  refs: ['level.warn'],
},