Skip to content
TrustedSkillsbeta
Back to all skills

Sast Eslint Security

Checked
vchirrav·vlatest·backend

Helps with ESLint, security as part of implementing security and authentication workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add vchirrav-eng/owasp-secure-coding-md --skill sast-eslint-security -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

vchirrav

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned vchirrav/owasp-secure-coding-md at a0f04031cb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a0f04031cb
Manifest
sast-eslint-security/SKILL.md
Scanned
1 file, 54 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill integrates ESLint security rules into a static analysis process. It analyzes JavaScript and TypeScript code to identify potential security vulnerabilities based on OWASP principles. The tool provides actionable feedback, helping developers proactively address common coding errors that could lead to exploits.

When to use it

  • Code Reviews: Integrate this skill into your automated code review pipelines to flag potential security issues early in the development lifecycle.
  • New Project Setup: Use this skill when initializing a new JavaScript or TypeScript project to enforce secure coding practices from the start.
  • Security Audits: Perform targeted scans of existing codebases to identify and remediate known vulnerabilities.
  • Training & Education: Help developers learn about common security pitfalls by providing clear, actionable feedback on their code.

Key capabilities

  • OWASP-based security ruleset
  • JavaScript and TypeScript support
  • Static analysis
  • Actionable vulnerability feedback
  • Integration with CI/CD pipelines (implied)

Example prompts

  • "Analyze this JavaScript file for potential security vulnerabilities."
  • "Run ESLint security checks on the src directory of my project."
  • "Find any code that violates OWASP secure coding guidelines in this TypeScript file."

Tips & gotchas

  • Requires Node.js and npm to be installed.
  • The effectiveness depends on the configuration of the ESLint ruleset; ensure it's appropriately configured for your specific needs.