Disclaimer

1. What Lintsure is

Lintsure is a readiness tool. It reads source code and some configuration files and points out places that may not meet the code-related parts of certain laws and standards: currently the EU AI Act, GDPR, SOC 2 and ISO/IEC 27001. It suggests fixes and lists the work that lives outside code.

2. What Lintsure is not

• Not an audit. No auditor examines your organization when you run Lintsure.
• Not a certification or attestation. Lintsure cannot certify you against ISO/IEC 27001, issue a SOC 2 report, or confirm conformity under the EU AI Act. Only accredited bodies, licensed auditors or the relevant authorities can do that.
• Not legal advice. Nothing Lintsure produces, including our website, docs, reports and the agents' replies, is legal advice. For legal questions, consult a qualified lawyer.
• Not a decision maker. Lintsure does not decide whether a law applies to you, whether you are compliant, or what risk you should accept.

3. A human in the loop, always

We build Lintsure on one rule: a person makes the final call. In practice:

• Lintsure suggests which frameworks may apply. You confirm them.
• Lintsure suggests fixes. Nothing changes until you, or someone you trust, reviews and approves the change.
• Every report ends with the steps a person still has to take, including a review by a qualified compliance professional before any audit, certification or business decision.
• The assessment report includes a human review and sign-off section. A report without that review is a draft.
• When used through a coding agent, Lintsure instructs the agent not to call you compliant, certified or ready, not to decide for you, and to ask before changing anything. The coding agent is a separate product made by another company, so we cannot guarantee how it follows those instructions.

4. It checks code only

Every framework Lintsure covers also needs work that code cannot show: policies, training, contracts with vendors, risk assessments, access reviews, incident handling, physical security and how your team actually works. Reports list these under "Outside code". Finishing the code side does not make you ready for a full review.

5. Our reading of public texts

Our rules and summaries reflect our own reading of publicly available texts: for example the EU AI Act and GDPR as published in the Official Journal of the European Union, regulator guidance, and the publicly listed control and criterion identifiers of ISO/IEC 27001 and SOC 2. We write our summaries in our own words. They do not reproduce, and are not a substitute for, the official texts or the licensed standards. Laws and standards change; our knowledge of each framework shows the date it was last checked.

6. Results can be wrong

• In version 0.1, all four frameworks and every rule are in Beta: rule mappings to framework controls await review by a qualified compliance professional.
• Rules look for patterns within a line or a file. They can miss real problems (false negatives) and can flag code that is fine (false positives).
• Rules mainly cover JavaScript, TypeScript and Python. Other code is mostly not checked.
• A control marked Met only means Lintsure's rules found no problem in the files they read. It does not mean the control is satisfied.
• Example data on this website, such as findings, file names and numbers in demos, is illustrative and not from a real customer.

7. No warranty

The open-source software is provided "as is", without warranties or conditions of any kind, under the Apache License 2.0. Use of this website and our services is covered by our Terms of use.

8. Questions

Email hello@lintsure.com, or support@lintsure.com for help with the product.