GitHub

audit.signedin

Someone signed in, the ordinary way

Profile

Logs

Written with

log()

Level

info
View as Markdown

Audit intents

Example

TS
log('audit.signedin', 'Something happened', {  });
Writes
TS
{
  "intent": "audit.signedin",
  "level": "info",
  "alert": false,
  "message": "Something happened",
  "data": {},
  "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

  • Someone signed in, the ordinary way

    audit.signedin this page

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

    security.signin

  • An ordinary sign-in

    rather than security.signin
    audit.signedin 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
'audit.signedin': {
  kind: 'semantic',
  description: 'Someone signed in, the ordinary way',
  refs: ['level.info'],
  notFor: [
    {
      context: 'a failed sign-in, or one from somewhere unusual',
      instead: 'security.signin',
    },
  ],
},