Skip to content

AI call with no record kept in this file

Partialmedium severity · reads .ts .tsx .js .jsx .mjs .cjs .pyBeta

High-risk systems must keep logs that let you trace what the AI did. Marked Partial: logging may happen in another file. When Lintsure finds this, it marks it as Partial: it may be fine, depending on context only you can confirm.

What it looks like

A line Lintsure flags in its own test app:

// src/ai.ts
const res = await openai.chat.completions.create({ model: "gpt", messages: [] });

How to fix it

Log each AI call: time, model and version, input reference and output, without raw personal data.

Through a coding agent, Lintsure suggests the change and waits. Nothing is edited until you approve it.

Controls it relates to

  • EU AI ActArt. 12Record-keeping
  • SOC 2CC7.2Monitoring of system components

What the framework asks

EU AI Act Art. 12: Record-keeping (logs)

The system should automatically log what it did, so events can be traced later.

Evidence a reviewer may ask for: Sample logs showing time, model version, input reference and output.

SOC 2 CC7.2–7.5: Monitoring and incidents

You watch for unusual activity, respond to incidents and recover.

Evidence a reviewer may ask for: Logs, alerts and an incident response plan.

ISO 27001 A.8.15–8.16: Logging and monitoring

Record important events, protect the logs and watch them for problems.

Evidence a reviewer may ask for: Log setup and alert rules.

Summaries are our own reading of the public texts, not the official wording.

Read more: The EU AI Act for developers

Check your code for this

Runs on your machine. Your code is never uploaded.

npx lintsure scan

Quickstart · Use it in Claude Code or Cursor

This rule is in Beta: its mapping to framework controls is waiting for review by a qualified compliance professional. Lintsure is a readiness tool, not an audit or legal advice. A finding, or the lack of one, doesn't make you compliant. Disclaimer

Related rules