CtrlK
BlogDocsLog inGet started
Tessl Logo

tessl-labs/express-security-basics

Security defaults that belong in every Express application from day one.

93

6.18x
Quality

90%

Does it follow best practices?

Impact

99%

6.18x

Average score across 5 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

cors-configured.jsonverifiers/

{
  "instruction": "Configure CORS with explicit allowed origins, not wildcard",
  "relevant_when": "Agent creates or modifies an Express application, adds routes to an Express app, or sets up an Express project",
  "context": "Every Express app that will be accessed from a browser needs CORS configured with explicit origins. Using cors() with no arguments allows any origin (Access-Control-Allow-Origin: *). Using origin: true reflects any request origin, which is dangerous with credentials. Always configure explicit allowed origins from environment variables.",
  "sources": [
    {
      "type": "file",
      "filename": "skills/express-security-basics/SKILL.md",
      "tile": "tessl-labs/express-security-basics@0.2.0"
    }
  ],
  "checklist": [
    {
      "name": "cors-not-wildcard",
      "rule": "Agent does not use cors() with no arguments, origin: '*', or origin: true in production config",
      "relevant_when": "Agent creates or modifies an Express application"
    },
    {
      "name": "cors-explicit-origins",
      "rule": "Agent configures CORS with specific allowed origins from environment variables or config (e.g., process.env.ALLOWED_ORIGINS)",
      "relevant_when": "Agent creates or modifies an Express application"
    },
    {
      "name": "cors-methods-restricted",
      "rule": "Agent specifies allowed HTTP methods rather than accepting all methods by default",
      "relevant_when": "Agent creates or modifies an Express application"
    }
  ]
}

tile.json