personal-finance / rules
Cursor rule1 starsChanged todayMITView on GitHub
TypeScript and JavaScript security: secrets, env vars exposed to the browser, tokens, untrusted input
- Reads credentials
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,243 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository84 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/angular-coding-style.mdcCursor rule
- .cursor/rules/angular-patterns.mdcCursor rule
- .cursor/rules/angular-security.mdcCursor rule
- .cursor/rules/angular-testing.mdcCursor rule
- .cursor/rules/common-code-review.mdcCursor rule
- .cursor/rules/common-coding-style.mdcCursor rule
- .cursor/rules/common-development-workflow.mdcCursor rule
- .cursor/rules/common-security.mdcCursor rule
- .cursor/rules/common-testing.mdcCursor rule
- .cursor/rules/csharp-coding-style.mdcCursor rule
- .cursor/rules/csharp-data-access.mdcCursor rule
- .cursor/rules/csharp-patterns.mdcCursor rule
- .cursor/rules/csharp-security.mdcCursor rule
- .cursor/rules/csharp-testing.mdcCursor rule
- .cursor/rules/design-design-system.mdcCursor rule
- .cursor/rules/project-backend.mdcCursor rule
- .cursor/rules/project-security.mdcCursor rule
- .cursor/rules/project-testing.mdcCursor rule
- .cursor/rules/project-web.mdcCursor rule
- .cursor/rules/typescript-coding-style.mdcCursor rule
- .cursor/rules/typescript-patterns.mdcCursor rule
- .cursor/rules/typescript-testing.mdcCursor rule
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- ui-ux-pro-maxSkill
- angular-guideSkill
- break-uiSkill
- dotnet-create-command-querySkill
- dotnet-create-entitySkill
- dotnet-create-moduleSkill
- dotnet-ef-migrationSkill
- emil-design-engSkill
- frontend-designSkill
- impeccableSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- The first 60 shown.
The file
We split this typescript-security.mdc into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
No secrets in source: Read them from the environment at startup and fail fast when they are missing.
- Very specific: line 18
Tokens never live in the browser's script-readable storage: not in localStorage, sessionStorage or a non-httpOnly cookie.
- Distinctive: line 21
Untrusted input is parsed with a schema: before use, including tool and model output.
- Very specific: line 26
Use the security-reviewer agent before a pull request that touches auth, input handling or dependencies.
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
---
description: "TypeScript and JavaScript security: secrets, env vars exposed to the browser, tokens, untrusted input"
globs: **/*.ts,**/*.tsx,**/*.js,**/*.jsx,**/.env.example
alwaysApply: false
---
<!-- Generated by armature from stack-typescript/rules/typescript/security.md. Edit the source rule, not this file. -->
# TypeScript security
- **No secrets in source.** Read them from the environment at startup and fail fast when they are missing.
```typescript
const apiKey = process.env.API_KEY
if (!apiKey) throw new Error('API_KEY not configured')
```
- **Public prefixes are public.** Anything with `NEXT_PUBLIC_`, `VITE_`, `PUBLIC_` or in an Angular `environment.ts`
ships in the browser bundle. Backend URLs, tokens and keys never get such a prefix.
- **Tokens never live in the browser's script-readable storage**: not in `localStorage`, `sessionStorage` or a
non-httpOnly cookie. Sessions are httpOnly, `Secure`, `SameSite=Lax` (or stricter) cookies.
- **Authorisation happens on the server.** Hiding a button is not access control; the API enforces every rule.
- **Untrusted input is parsed with a schema** before use, including tool and model output.
- **No HTML from strings** (`innerHTML`, `dangerouslySetInnerHTML`, `bypassSecurityTrust*`) unless sanitised at the
same call site with an allow-list sanitiser (DOMPurify).
- **URLs from users** are checked for scheme (`http:`, `https:`, `mailto:` only) before going into `href` or `src`.
- **Dependencies:** pin exact versions for anything security-relevant; read the changelog before a major upgrade.
- Use the `security-reviewer` agent before a pull request that touches auth, input handling or dependencies.
<!-- Adapted from affaan-m/ECC rules/typescript/security.md and rules/react/security.md (MIT) at d2ef268; merged with the owner's conventions (ordo-frontend: server-only BACKEND_URL, tokens only in the server session). -->
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

