# Codecov Configuration for ofri-peretz/eslint monorepo # https://docs.codecov.com/docs/codecov-yaml coverage: precision: 0 round: down range: '70...100' status: project: default: target: 100% patch: default: target: 100% # ═══════════════════════════════════════════════════════════════════════════════ # FLAGS — per-plugin uploads (used for badge URLs) # Badge URL: https://codecov.io/gh/ofri-peretz/eslint/graph/badge.svg?flag= # carryforward: FALSE - a report shows what this commit actually measured. # # It was true, as a safety net for runs that did not upload every plugin. That # net turned into the problem. Uploads were skipped wholesale whenever a single # package missed its threshold (8 of 13 scheduled runs uploaded nothing at all, # fixed in #866), and node-security never uploaded at all because it wrote its # lcov outside the path the workflow reads (#867). Carryforward kept serving the # last value each flag ever sent, so the numbers stayed plausible and stopped # moving - node-security sat at a fossilised 99.80% against a measured 100%, and # nothing looked broken enough to investigate. # # It also merges a carried session into the current one, which is the leading # explanation for the components publishing less than the 100% their lcov # reports: Codecov holds 10,565 lines for secure-coding where we upload 5,328, # the surplus all missed, across the same 38 files. # # Every package now uploads on every run, so there is nothing to carry. A flag # that goes missing should read as missing - that gets investigated. A stale # number that looks right does not. # ═══════════════════════════════════════════════════════════════════════════════ flags: eslint-devkit: paths: [packages/eslint-devkit/] carryforward: false eslint-formatter: paths: [packages/eslint-formatter/] carryforward: false eslint-plugin-browser-security: paths: [packages/eslint-plugin-browser-security/] carryforward: false eslint-plugin-conventions: paths: [packages/eslint-plugin-conventions/] carryforward: false eslint-plugin-express-security: paths: [packages/eslint-plugin-express-security/] carryforward: false eslint-plugin-import-next: paths: [packages/eslint-plugin-import-next/] carryforward: false eslint-plugin-jwt-security: paths: [packages/eslint-plugin-jwt-security/] carryforward: false eslint-plugin-lambda-security: paths: [packages/eslint-plugin-lambda-security/] carryforward: false eslint-plugin-maintainability: paths: [packages/eslint-plugin-maintainability/] carryforward: false eslint-plugin-modernization: paths: [packages/eslint-plugin-modernization/] carryforward: false eslint-plugin-modularity: paths: [packages/eslint-plugin-modularity/] carryforward: false eslint-plugin-mongodb-security: paths: [packages/eslint-plugin-mongodb-security/] carryforward: false eslint-plugin-nestjs-security: paths: [packages/eslint-plugin-nestjs-security/] carryforward: false eslint-plugin-node-security: paths: [packages/eslint-plugin-node-security/] carryforward: false eslint-plugin-operability: paths: [packages/eslint-plugin-operability/] carryforward: false eslint-plugin-postgresql-security: paths: [packages/eslint-plugin-postgresql-security/] carryforward: false eslint-plugin-react-a11y: paths: [packages/eslint-plugin-react-a11y/] carryforward: false eslint-plugin-react-features: paths: [packages/eslint-plugin-react-features/] carryforward: false eslint-plugin-reliability: paths: [packages/eslint-plugin-reliability/] carryforward: false eslint-plugin-secure-coding: paths: [packages/eslint-plugin-secure-coding/] carryforward: false eslint-plugin-vercel-ai-security: paths: [packages/eslint-plugin-vercel-ai-security/] carryforward: false comment: layout: 'header, diff, flags, components' behavior: default require_changes: false # ═══════════════════════════════════════════════════════════════════════════════ # TEST ANALYTICS (https://docs.codecov.com/docs/test-analytics) # ═══════════════════════════════════════════════════════════════════════════════ # Tracks test run times, failure rates, and flaky tests # JUnit XML reports are uploaded via codecov/test-results-action in CI # ═══════════════════════════════════════════════════════════════════════════════ # COMPONENT MANAGEMENT FOR MONOREPO # ═══════════════════════════════════════════════════════════════════════════════ # Each package gets its own component for separate coverage tracking component_management: default_rules: statuses: - type: project target: 100% - type: patch target: 100% individual_components: # ───────────────────────────────────────────────────────────────────────── # Security Plugins (Primary) # ───────────────────────────────────────────────────────────────────────── - component_id: eslint-plugin-secure-coding name: 'eslint-plugin-secure-coding' paths: - packages/eslint-plugin-secure-coding/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-formatter-sarif name: 'eslint-formatter-sarif' paths: - packages/eslint-formatter-sarif/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-formatter name: 'eslint-formatter' paths: - packages/eslint-formatter/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-jwt-security name: 'eslint-plugin-jwt-security' paths: - packages/eslint-plugin-jwt-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-postgresql-security name: 'eslint-plugin-postgresql-security' paths: - packages/eslint-plugin-postgresql-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-mongodb-security name: 'eslint-plugin-mongodb-security' paths: - packages/eslint-plugin-mongodb-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-node-security name: 'eslint-plugin-node-security' paths: - packages/eslint-plugin-node-security/** statuses: - type: project target: 100% - type: patch target: 100% # ───────────────────────────────────────────────────────────────────────── # Framework Security Plugins # ───────────────────────────────────────────────────────────────────────── - component_id: eslint-plugin-express-security name: 'eslint-plugin-express-security' paths: - packages/eslint-plugin-express-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-nestjs-security name: 'eslint-plugin-nestjs-security' paths: - packages/eslint-plugin-nestjs-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-lambda-security name: 'eslint-plugin-lambda-security' paths: - packages/eslint-plugin-lambda-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-browser-security name: 'eslint-plugin-browser-security' paths: - packages/eslint-plugin-browser-security/** statuses: - type: project target: 100% - type: patch target: 100% # ───────────────────────────────────────────────────────────────────────── # AI Security Plugins # ───────────────────────────────────────────────────────────────────────── - component_id: eslint-plugin-vercel-ai-security name: 'eslint-plugin-vercel-ai-security' paths: - packages/eslint-plugin-vercel-ai-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-anthropic-security name: 'eslint-plugin-anthropic-security' paths: - packages/eslint-plugin-anthropic-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-gemini-security name: 'eslint-plugin-gemini-security' paths: - packages/eslint-plugin-gemini-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-openai-security name: 'eslint-plugin-openai-security' paths: - packages/eslint-plugin-openai-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-mcp-sdk-security name: 'eslint-plugin-mcp-sdk-security' paths: - packages/eslint-plugin-mcp-sdk-security/** statuses: - type: project target: 100% - type: patch target: 100% # ───────────────────────────────────────────────────────────────────────── # SQL / ORM Driver Plugins # # The newest surface and, until now, the least measured: every one of these # shipped without a component, so a coverage regression in any of them was # invisible on the dashboard while the repo-wide number stayed green. # ───────────────────────────────────────────────────────────────────────── - component_id: eslint-plugin-drizzle-security name: 'eslint-plugin-drizzle-security' paths: - packages/eslint-plugin-drizzle-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-knex-security name: 'eslint-plugin-knex-security' paths: - packages/eslint-plugin-knex-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-mysql-security name: 'eslint-plugin-mysql-security' paths: - packages/eslint-plugin-mysql-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-prisma-security name: 'eslint-plugin-prisma-security' paths: - packages/eslint-plugin-prisma-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-sequelize-security name: 'eslint-plugin-sequelize-security' paths: - packages/eslint-plugin-sequelize-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-supabase-security name: 'eslint-plugin-supabase-security' paths: - packages/eslint-plugin-supabase-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-sqlite-security name: 'eslint-plugin-sqlite-security' paths: - packages/eslint-plugin-sqlite-security/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-typeorm-security name: 'eslint-plugin-typeorm-security' paths: - packages/eslint-plugin-typeorm-security/** statuses: - type: project target: 100% - type: patch target: 100% # ───────────────────────────────────────────────────────────────────────── # Governance & Quality Plugins # ───────────────────────────────────────────────────────────────────────── - component_id: eslint-plugin-conventions name: 'eslint-plugin-conventions' paths: - packages/eslint-plugin-conventions/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-maintainability name: 'eslint-plugin-maintainability' paths: - packages/eslint-plugin-maintainability/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-modernization name: 'eslint-plugin-modernization' paths: - packages/eslint-plugin-modernization/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-modularity name: 'eslint-plugin-modularity' paths: - packages/eslint-plugin-modularity/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-operability name: 'eslint-plugin-operability' paths: - packages/eslint-plugin-operability/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-reliability name: 'eslint-plugin-reliability' paths: - packages/eslint-plugin-reliability/** statuses: - type: project target: 100% - type: patch target: 100% # ───────────────────────────────────────────────────────────────────────── # Core Packages # ───────────────────────────────────────────────────────────────────────── - component_id: eslint-devkit name: 'eslint-devkit' paths: - packages/eslint-devkit/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-import-next name: 'eslint-plugin-import-next' paths: - packages/eslint-plugin-import-next/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-react-features name: 'eslint-plugin-react-features' paths: - packages/eslint-plugin-react-features/** statuses: - type: project target: 100% - type: patch target: 100% - component_id: eslint-plugin-react-a11y name: 'eslint-plugin-react-a11y' paths: - packages/eslint-plugin-react-a11y/** statuses: - type: project target: 100% - type: patch target: 100% # NOTE: cli is an infrastructure package without tests - excluded # ═══════════════════════════════════════════════════════════════════════════════ # IGNORE PATHS # ═══════════════════════════════════════════════════════════════════════════════ # Files that don't contain runtime logic or lack tests. # # ── Everything outside packages/ ─────────────────────────────────────────────── # # Codecov is the CONSUMER-FACING number. It answers "is the code you install # tested", so its denominator is the code that ships: packages/. Internal # tooling is measured by whether it works, not by a coverage percentage. # # These paths were never uploaded — the workflow runs `turbo run test:coverage` # over packages only — so listing them changes no number. What it changes is # that the omission becomes a DECISION rather than an accident. An absent path # and a deliberately excluded one look identical in a report; that difference # is the whole reason every artefact in this repo carries a `command` field. # # Measured before deciding, so the trade is on the record: # # scripts/ 176 source files, 7.95% line coverage # benchmarks/ 361 # apps/ 257 # tools/ 6 # # scripts/ is the interesting one and the answer is still no. It holds the # gates, and this repo has repeatedly shipped wrong numbers because a gate was # broken — a swallowed ReferenceError that made an artefact read STALE for # months, a lock that passed because it asserted its own prose. But those are # caught by scripts/__tests__ (125 files, 2,505 tests), which is a correctness # signal, not a percentage. Raising 7.95% to a gate would be a large project # for code no consumer ever receives, and it would put a second, louder number # next to the one customers actually read. # # If that calculus changes, the honest move is a SEPARATE Codecov project for # tooling, not diluting this one. ignore: # ── Packages that never reach a consumer ────────────────────────────────── # # `private: true` means npm will refuse to publish it, so no user can install # it and it has no business in a number that answers "is the code you install # tested". Same rule as the tooling trees below, applied inside packages/. # # These carried most of the 311 lines three packages once added to the # report's 32,016. Both formatters have since left this list on the same # rule — they ship, so they are measured, not ignored. - 'packages/ui/**' # Built and tested, not yet published: drop this line when it ships. - 'packages/eslint-plugin-cli-floor/**' # oxlint-plugin-* ship no code of their own: each alias is a one-line # re-export of an eslint-plugin-* that IS measured, and the security façade # is built from mapping.json. See docs/intents/oxlint-native-plugin-names. - 'packages/oxlint-plugin-*/**' - 'apps/**' - 'scripts/**' - 'benchmarks/**' - 'tools/**' - '**/*.test.ts' - '**/*.spec.ts' - '**/node_modules/**' - '**/dist/**' - '**/.nx/**' - '**/types/**' - '**/types/index.ts' - '**/coverage/**' - '**/test-results/**' - '**/*.config.ts' - '**/*.config.mts' - '**/vitest.global-setup.ts'