security.signin

A sign-in failed, or succeeded from somewhere unusual

Profile

Written with

Level

warn

Security intents

Example

TS
log('security.signin', 'Sign-in failed', { email: 'ada@example.com', attempts: 3 });
Writes
TS
{
"intent": "security.signin",
"level": "warn",
"alert": false,
"message": "Sign-in failed",
"data": {
"email": "ada@example.com",
"attempts": 3
},
"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 sign-in failed, or succeeded from somewhere unusual

    security.signin this page
  • An ordinary sign-in

    audit.signedin
  • A failed sign-in, or one from somewhere unusual

    rather than audit.signedin
    security.signin 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.signin': {
kind: 'semantic',
description: 'A sign-in failed, or succeeded from somewhere unusual',
refs: ['level.warn'],
notFor: [{ context: 'an ordinary sign-in', instead: 'audit.signedin' }],
},