Every rule your AI software might need to meet
AI laws, privacy rules, security standards and industry rules, in one list. Tell us what you build and we'll suggest which ones apply. Lintsure checks each one in your code as its rules ship.
Ask a question about a framework. Get the answer from your code.
Yes. ml/score.py makes automated credit decisions, which the EU AI Act lists as high-risk. Article 14 asks for a way for a person to review and override them. There is no override path yet.
Found in
- Partialml/score.py:18Score is logged but never shown to a reviewer
- Gapapi/decisions.ts:40Decision is final, no override endpoint
Outside code
Risk management process · Art. 9. Lintsure lists it for the Officer agent instead of guessing.
Partly. DELETE /account removes the user row but keeps their email in analytics events. Article 17 says erase it everywhere you hold it.
Found in
- Partialapi/account.ts:88Deletes the user, not their events
- Gapjobs/analytics.ts:12Email copied into event payload
Outside code
Records of processing · Art. 30. Lintsure lists it for the Officer agent instead of guessing.
For user changes, yes. For billing, no. CC7.2 expects you to log security-relevant events and watch them.
Found in
- Metadmin/users.ts:51Role changes written to audit log
- Gapadmin/billing.ts:23Refunds change data with no log entry
Outside code
Quarterly access reviews · CC6.2. Lintsure lists it for the Officer agent instead of guessing.
Not yet. One live key is hardcoded. Control A.8.24 asks you to manage keys, not commit them.
Found in
- Gapconfig/stripe.ts:4Live secret key in source
- Met.env.example:1Placeholders only, no real values
Outside code
Supplier security agreements · A.5.20. Lintsure lists it for the Officer agent instead of guessing.
Pick the rules that apply to what you build
Answer four questions and Lintsure suggests a set. Change anything you like, then copy the config. Or skip this: the Classifier reads your repo and suggests the same list, and you confirm it.
0 selected · 0 more apply, coming later
4 available now · 28 on the roadmap
AI laws and standards
Privacy and data protection
Security frameworks
Industry rules
lintsure.config.yaml
"Planned" frameworks are greyed out because we don't check them yet. "Platform" ones will be specialist rule packs on the paid platform; the rest join the free tool. If your answers say one applies, it's marked "Applies to you" so you know it's coming. Lintsure never shows a framework as covered before its rules ship. Suggestions are a starting point, not legal advice.
Rule sets, ready to run
EU AI Act · GDPR · SOC 2 · ISO/IEC 27001 · more as they ship
maps: Art. 32
status: met | partial | gapsoc2/secrets.yamlid: secret.in-source
maps: CC6.1
status: met | partial | gapeu-ai-act/oversight.yamlid: decision.no-override
maps: Art. 14
status: met | partial | gapiso-27001/keys.yamlid: crypto.key-managed
maps: A.8.24
status: met | partial | gapsoc2/audit-log.yamlid: admin.audit-log
maps: CC7.2
status: met | partial | gapgdpr/erasure.yamlid: user.delete-path
maps: Art. 17
status: met | partial | gap