Skip to content

Data sent over plain HTTP

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

Marked Partial: the call may carry no sensitive data. Confirm, then switch to HTTPS anyway. 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/billing.ts
return fetch("http://payments.example.com/charge", { method: "POST", body });

How to fix it

Use https:// for every external call.

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

Controls it relates to

  • SOC 2CC6.7Transmission of data
  • ISO 27001A.8.20Network security
  • GDPRArt. 32Security of processing

What the framework asks

GDPR Art. 32: Security of processing

Protect personal data with security that fits the risk: encryption, access control, testing and the ability to recover.

Evidence a reviewer may ask for: Security measures and when they were last tested.

SOC 2 CC6.7: Data in transit

Data moving between systems is protected, usually with properly verified TLS.

Evidence a reviewer may ask for: TLS settings and certificate checks.

ISO 27001 A.8.20: Network security

Networks and connections are protected and controlled.

Evidence a reviewer may ask for: Network and TLS settings.

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

Read more: Which SOC 2 controls you can check in code

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