saleor-dashboard-security-audit
Skill1.1k starsChanged 8 days agoBSD-3-ClauseView on GitHub
Triage OSV and `pnpm audit` security findings and propose batched, accept-first dependency fixes. Use when asked to run a security audit, fix security vulnerabilities, update vulnerable packages, or analyze dependency audit output.
- Installs packages
Trending
Less talk lately.about the whole repository
Who's talking about saleor/saleor-dashboard
- saleor/saleor“Unable to update Company info from Dashboard”GitHub · May 31, 2022 · 2 reactions
- saleor/apps“Implement logo field in AppManifest”GitHub · Feb 22, 2023 · 1 reactions
- saleor/saleor“Support for payment transaction actions”GitHub · Aug 11, 2022 · 1 reactions
- saleor/saleor“feat(attribute): add staff-only internalDescription to Attribute”GitHub · Oct 15, 2026
- waelhe/app-java-v3“docs(admin): plan Saleor Dashboard adaptation for marketplace”GitHub · Oct 15, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- May 31, 2022Unable to update Company info from Dashboard — saleor/saleor2 reactions · 3 comments
- Feb 22, 2023Implement logo field in AppManifest — saleor/apps1 reaction · 3 comments
- Aug 11, 2022Support for payment transaction actions — saleor/saleor1 reaction · 27 comments
- Oct 15, 2026feat(attribute): add staff-only internalDescription to Attribute — saleor/saleor0 reactions · 1 comment
- Oct 15, 2026docs(admin): plan Saleor Dashboard adaptation for marketplace — waelhe/app-java-v30 reactions · 3 comments
45 more on GitHub
- Jul 31, 2026feat(avatax): add tax code action to Dashboard command palette — saleor/apps0 reactions · 5 comments
- Jul 13, 2026Add reason for price override — saleor/saleor0 reactions · 1 comment
- Jul 8, 2026Improved Gift Card APIs — saleor/saleor0 reactions · 1 comment
- Jun 9, 2026[Feature] Support pasting boolean values in other that English — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026Fix Background task provider tests — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missing filter when calling exportGiftCards mutation for selected giftcards — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Variant view, no scroll on warehouse list and only first 50 warehouses displayed for the user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: `requestPasswordReset` mutation returns incorrect error when user is not staff user — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Missed info about no access to the channels — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026 `create order` button should be disabled in case of no permissions — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026User can create group with permission from plugin but cannot assign members via UI — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Enhancement]: Misleading UI when charge is pending — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Modal leave without saving after logout — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Feature]: Change navigation structure — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Only first 50 warehouses are loaded in the grid — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Weight rate create - not consistent error messages — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Price rate and weight base availability button inactive — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Changing attribute value on product triggers SKU fail — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Restrict order weight in shipping method not saved — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Datagrids jump to end when resizing column — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Enable refunding specific product lines — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Deleting variant attribute changes variant name — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Column picker refinement — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026No information about required fields in product variant form — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026Error handling in product variant page - user can delete required field and still be able to save - then success banner shows up followed by error banner — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Remove add product — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Not all attributes are validated — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Error label misplaced — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Error messages missmatch — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Epic]: Improve UX flow for order refunds using Transactions API — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: Can not refund fulfilled order — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: Incorrect background in label cell — WillSmithTE/saleor-saleor-dashboard0 reactions
- Jun 9, 2026[Bug]: City and Postal code is getting cleared while modifying and saving the country field and country area in warehouse modification — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]:Error displayed while selecting Category name header checkbox and click pagination in category Listing Page — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 9, 2026[Bug]: dashboard not using all settings field in query (Can't set limitQuantityPerCheckout) — WillSmithTE/saleor-saleor-dashboard0 reactions · 1 comment
- Jun 3, 2026Add support for editorJS table syntax — saleor/saleor0 reactions · 1 comment
- May 5, 2026HOMEPAGE_WIDGETS types for manifest — saleor/app-sdk0 reactions · 2 comments
- Mar 25, 2026Fix LSP not loading `.js` and `.ts` files correctly — graphql/graphiql0 reactions · 5 comments
- Mar 13, 2026Add proper gift card events when gift card is used as a payment method — saleor/saleor0 reactions · 1 comment
- Mar 12, 2026Fix smoke tests - add prefix for artifact upload — saleor/apps0 reactions · 3 comments
- Mar 6, 2026Introduce password login mode — saleor/saleor0 reactions · 2 comments
- Mar 5, 2026Add SaleorGiftcardPaymentMethodDetails to transaction — saleor/saleor0 reactions · 2 comments
- Feb 25, 2026Fix failing smoke tests workflow — saleor/apps0 reactions · 3 comments
- Feb 13, 2026document payment method details in dashboard — saleor/saleor-docs0 reactions · 1 comment
- Feb 10, 2026Refund reasons phase 2 (POC) — saleor/saleor0 reactions · 1 comment
In this repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pinactSkill
- saleor-dashboard-cloud-extensionsSkill
- saleor-dashboard-detail-pagesSkill
- saleor-dashboard-entity-detailSkill
- saleor-dashboard-feedbackSkill
- saleor-dashboard-formsSkill
- saleor-dashboard-github-workflowsSkill
- saleor-dashboard-graphql-batchingSkill
- saleor-dashboard-listsSkill
- saleor-dashboard-loadingSkill
- saleor-dashboard-microcopySkill
- saleor-dashboard-pr-quality-checkSkill
- saleor-dashboard-smooth-shadowSkill
- saleor-dashboard-stylesSkill
The file
We split this skill 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 12
When applying fixes you install dependencies — the exact moment a malicious or compromised package would land on the machine.
- Very specific: line 23
If sfw is missing, install it first with npm i -g sfw (binaries for macOS/Linux/Windows are on the releases page).
- Very specific: line 43
Run both scanners. OSV is the advisory inventory because it checks every package/version in pnpm-lock.yaml against the databases aggregated …
- Distinctive: line 119
Batch D — A large single-package cluster: if one bump clears many findings (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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
Dependency Security Audit & Fix Triage
Goal: turn dependency audit findings into a small set of accept-first batches the user can approve and merge independently. Do NOT apply fixes until the user accepts the proposal. NEVER fix everything in one commit.
Always install through Socket Firewall (sfw)
When applying fixes you install dependencies — the exact moment a malicious or
compromised package would land on the machine. Never run a bare pnpm install
in this workflow. Wrap every install with Socket Firewall Free,
which scans dependencies in real time and blocks known-malicious ones before
they reach disk:
sfw pnpm install # instead of `pnpm install`
sfw pnpm install --frozen-lockfileIf sfw is missing, install it first with npm i -g sfw (binaries for
macOS/Linux/Windows are on the releases page). Same pattern for any other
manager: sfw <package-manager> <command>.
How this repo fixes vulnerabilities
Most findings are transitive (deep in the dep tree). This repo does NOT bump those individually — it pins them via pnpm-workspace.yaml → overrides: (the single source of truth; never use package.json → pnpm.overrides). Direct deps are bumped in package.json.
Key config already in pnpm-workspace.yaml:
overrides:— pin a transitive (or direct-via-resolution) package to a patched range, e.g."ws@>=8.0.0 <8.21.0": ">=8.21.0". To fix an existing-but-outdated override, widen its range — don't add a duplicate key.minimumReleaseAge: 30240(= 21 days). New installs must be ≥21 days old. A patched version released < 21 days ago will be rejected unless added tominimumReleaseAgeExclude.minimumReleaseAgeExclude:— per-package bypass of the age gate (used sparingly, with a comment explaining why).auditConfig.ignoreCves:— CVEs intentionally accepted (e.g. minimatch ReDoS variants that only affect dev/build tools and whose fix breaks CJS consumers). Check this before proposing a fix — it may already be a deliberate accept.trustPolicy: no-downgrade+trustPolicyExclude:— provenance/signing gate.
Procedure
1. Collect & parse
Run both scanners. OSV is the advisory inventory because it checks every
package/version in pnpm-lock.yaml against the databases aggregated by OSV.
pnpm audit supplements it with pnpm dependency paths and npm-specific
remediation data; do not treat it as the complete advisory source.
OSV-Scanner is required; if it is missing, install the official binary (on
macOS with Homebrew: brew install osv-scanner) rather than skipping this scan.
osv_status=0
osv-scanner scan source -L pnpm-lock.yaml --format json > /tmp/osv-audit.json || osv_status=$?
if [ "$osv_status" -gt 1 ]; then exit "$osv_status"; fi
pnpm audit --json > /tmp/pnpm-audit.jsonOSV-Scanner exits with status 1 when it finds vulnerabilities, so only statuses
greater than 1 are scanner errors. Parse /tmp/osv-audit.json first, merging
records by id and aliases, then join the pnpm findings by package and
installed version.
In the pnpm JSON, actions only suggests partial fixes. Each advisory carries:
module_name, severity, patched_versions, vulnerable_versions, title,
github_advisory_id, url, cwe, and findings[].version /
findings[].paths. The dependency path (top-level dep = 2nd path segment;
path.split(">").length === 2 means it's a direct dep) tells you
direct-vs-transitive. Useful one-liner:
node -e '
const a=Object.values(JSON.parse(require("fs").readFileSync("/tmp/pnpm-audit.json","utf8")).advisories);
const o={critical:0,high:1,moderate:2,low:3};
a.sort((x,y)=>(o[x.severity]-o[y.severity])||x.module_name.localeCompare(y.module_name));
for(const v of a){const p=v.findings.flatMap(f=>f.paths);
const tops=[...new Set(p.map(s=>s.split(">")[1]||s))];const direct=p.some(s=>s.split(">").length===2);
console.log(`[${v.severity}] ${v.module_name} ${v.findings.map(f=>f.version)} -> ${v.patched_versions} ${v.github_advisory_id} ${direct?"DIRECT":""}\n ${v.title}\n via: ${tops.join(" | ")}`);}'Note — no CVSS in
pnpm auditoutput. pnpm's audit JSON does not include acvssfield (onlyseverity). For full details on a record found by OSV-Scanner, use the OSV API. It accepts either the OSV/GHSA ID or its CVE alias:curl -fsSL "https://api.osv.dev/v1/vulns/GHSA-479c-33wc-g2pg" curl -fsSL "https://api.osv.dev/v1/vulns/CVE-2026-23869"Check
aliasesfor the corresponding CVE/GHSA IDs andseverityfor CVSS vectors. When OSV has no quantitative score, use the source database's severity; usepnpm audit's severity only for pnpm-only metadata.
2. Check the age gate for every proposed target
For each patched version you intend to pin, confirm it's ≥21 days old (released before today − 21d):
npm view <pkg> time --json # find the patched version's publish date- Age OK → safe to pin/bump normally.
- Too new → prefer the oldest age-OK version that still satisfies
patched_versions(a partial fix that clears most advisories is fine — note what's left). Only bypass viaminimumReleaseAgeExcludeif severity requires it (critical, or production-path high with no age-OK fix), and only after asking for authorization. Document the bypass with a comment + advisory link.
3. Prioritize (in order)
- Severity first — criticals (RCE, injection) before highs before moderate/low.
pnpm auditno longer emits CVSS, so sort byseverity; if you need a quantitative tiebreak, look up the advisory by GHSA/CVE ID in OSV and use its CVSS vector. - Patch over major — a major bump (e.g.
uuid9→11) is a breaking change; split it out as its own effort needing code review, never bundle it into a routine audit batch. - Group related packages — one override often clears many advisories (e.g. a single
dompurifybump cleared ~9 findings; onepicomatch/ws/brace-expansionbump covers all paths). Bump tool families together (eslint + plugins, all@graphql-codegen/*, etc.). - Prefer the older age-OK fix over bypassing the age gate (see step 2).
4. Propose batches (do NOT apply yet)
Split into small, independently-mergeable batches. A good default split:
- Batch A — Criticals (RCE/injection). Smallest, highest urgency, merge first.
- Batch B — Direct-dep bumps (e.g.
vite,qs) — isolatedpackage.jsonchanges that touch build/runtime. - Batch C — High transitive overrides (grouped: picomatch, ws, brace-expansion…).
- Batch D — A large single-package cluster if one bump clears many findings (e.g. dompurify).
- Batch E — Moderate/low transitive overrides.
- Batch F — Deferred / needs-decision: fixes whose only patch is too-new (bypass-or-wait), major breaking bumps, and CVEs already in
auditConfig.ignoreCves. Present these as explicit choices, don't silently skip them.
Present a report: per batch list package, current→target, severity (+ GHSA id / CVE), dep path, age status, and the exact pnpm-workspace.yaml / package.json edit. Ask the user which batches to apply.
5. After acceptance (per batch)
- Edit
pnpm-workspace.yamloverrides (orpackage.jsonfor direct deps). sfw pnpm installto updatepnpm-lock.yaml(always through Socket Firewall — see above).- Re-run both OSV-Scanner and
pnpm auditto confirm the targeted findings are gone and nothing regressed. - For build/runtime-affecting deps (
vite, etc.), runpnpm run build/ relevant tests. - One commit per batch. Skip changesets — dependency security bumps are internal (see
saleor-dashboard-changesets).
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.

