dsh-ppap-check
Manifest validPPAP ?????????(???? PPAP ??????????????????,?????,???????)
dsh-ppap-check
Boundary: this plugin checks a PPAP 提交要素清单 for what a checklist can be held to mechanically — that an element the customer required carries a submission record, that a submitted element carries a date, that a controlled element (design record, FMEA, control plan, process flow, dimensional results, MSA) carries a revision, that the sheet names its part number and submission level, that element numbers are unique, and that no template placeholder survives. It does not decide whether PPAP may be approved, whether the level is right, or whether an element's content satisfies the customer. The submission level is the customer's to set, and this plugin ships no level-to-element mapping.
⚠️ Read this before trusting a citation in the report
Every
excerptin this plugin's rule pack says, in so many words, that the clause text was not obtained. The method lives in the automotive AIAG《生产件批准程序(PPAP)手册》 (and the customer specific requirements under IATF 16949). The verification pass could not retrieve verbatim clause text, so rather than paraphrase a quotation the pack states the gap in theexcerptfield itself and puts the honest reasoning innote. Every rule is thereforewarnorinfo, and a test asserts that no rule claims a quotation it does not have. When the text is in hand, two things must be done: replace eachexcerptwith the real clause, and raisekindtodirect.Which elements must be submitted depends on the level the customer specifies (Level 1–5), so
PP-001reads the checklist's own 是否要求 column rather than any built-in list, andPP-005's level vocabulary ships empty — with no vocabulary configured it reports itself inskippedinstead of passing quietly.
Compatibility
| Surface | Status |
|---|---|
| Harness | Peer range >=0.1.2-rc.1 <0.2.0 || >=0.2.0-0 <0.3.0 — verified to accept both 0.2.0-rc.2 and 0.2.1-alpha.1. engines.dsh is deliberately not declared: it has no reader and cannot reject a host |
| Node | `^22.19.0 |
| Platforms | All (plain ESM; no native code, no network, no model call) |
| Tool mode | Works in native, ptc and both; for several parts use ptc |
What it does
Registers the ppap_check tool. It reads one submission-element checklist — the part header plus one row per
element — applies a versioned rule pack, and returns a report.
| Rule | Check | Severity | Basis kind |
|---|---|---|---|
PP-001 | a required element has a submission record | warn | principle |
PP-002 | a submitted element carries a date | warn | principle |
PP-003 | a controlled element carries a revision | warn | principle |
PP-004 | the sheet names its part number and level | warn | principle |
PP-005 | the level comes from your customer's vocabulary (off by default) | info | local |
PP-006 | the element column holds no unreplaced placeholder | warn | principle |
PP-007 | element numbers are unique | warn | principle |
Install
pnpm pack
dsh plugin --profile <name> add ./dsh-ppap-check-0.1.0.tgz
dsh --profile <name> --dump-config | grep 'dsh-ppap-check'
Configuration
| Key | Type | Default | Description |
|---|---|---|---|
rulesFile | string | rules/ppap-check.yaml | Rule-pack path, relative to the package root |
disabledRules | string[] | [] | Rule ids to stop running; each appears in skipped |
onlyRules | string[] | [] | Run only these rule ids; empty runs every rule |
skipNotes | string | "" | Note appended to every skipped reason |
timeoutMs | number | 120000 | Cooperative tool timeout budget |
Rule-level parameters worth knowing:
PP-001conditionValues— the values in your 是否要求 column that mean "required", by default[是, Y, yes, true, 要求, √].PP-002conditionValues— the values in your 是否提交 column that mean "submitted".PP-003conditionPattern— the element names that carry revisions; the default covers design records, engineering changes, DFMEA/PFMEA, control plans, process flows, dimensional results, MSA, samples, checking aids, PSW, material reports and preliminary capability studies.PP-005values— your customer's level spellings, e.g.[Level 1, Level 2, Level 3, Level 4, Level 5]. Empty means no check.
Material format
The tool accepts JSON or YAML:
partNo: P-2026-001
partName: 前支架
supplier: 某某零部件有限公司
level: Level 3
rows:
- { 序号: '1', 提交要素: 设计记录, 是否要求: 是, 是否提交: 是,
提交日期: 2026-03-05, 版本: B, 责任人: 张工 }
Column names are matched case-insensitively and ignoring spaces, underscores and hyphens; the sheet's own column names are kept, so a finding names the column it read.
Rule sources
Rule data lives in rules/ppap-check.yaml. The pack's header states the citation gap in full, and each
rule's note repeats the part that matters for that rule. The load-time guard that normally enforces "an
excerpt must be a real quotation of at least eight characters" cannot tell a quotation from a description —
so this pack leans on the header, the per-rule notes and a test that asserts every excerpt admits the gap.
Troubleshooting
PP-005never runs. Its vocabulary is empty. Level spellings differ between customers, so the plugin will not guess them.PP-001fires on an element I do not intend to submit. The 是否要求 column says it is required. If the element is not required at your customer's level, correct that column rather than deleting the row.PP-003fires on an element with no revision. The element's name matches the pattern but the version column is empty. NarrowconditionPatternif your checklist has an element that genuinely carries no revision.- The plugin installs but the tool never appears. Check that
mainresolves tolib/index.mjsand thatpnpm run buildproduced it; a wrongmainmakes the loader skip the entry silently. dsh plugin addrefuses the package as incompatible. The peer range covers0.1.xand0.2.x; if your runtime sits outside it, grant an explicit exemption:dsh plugin --profile <name> allow-version dsh-ppap-check@0.1.0 --dsh-version <runtime> --accept-riskcheckreportsmanifest-peersas failed. The static checker compares against a hard-coded peer range that predates the 0.2 line. The runtime enforces peer compatibility at install time, so the declared range is the correct one; this is a known upstream issue indsh-plugin-dev.
Development
pnpm install
pnpm run typecheck # tsc --noEmit
pnpm test # vitest, the shared table-plugin suite plus paired fixtures
pnpm run build # tsdown -> lib/index.mjs + lib/index.d.mts
node ../scripts/sync-shared.mjs dsh-ppap-check # refresh src/shared from ../_shared
The plugin is data-only: src/model.ts declares the table shape, the shared kit supplies the reader and
the check engine, and the rule pack declares every check.
License
Apache License 2.0 © 2026 dsh-ppap-check contributors.
Comments
Loading…
Similar plugins
by PerryLink
??????????????(????????????,?????,???????)
★ 0
NOASSERTION
TypeScript
Oct 9, 2026
dsh plugin --profile web add dsh-archive-checkby PerryLink
????????(?????????????????????,?????,???????)
★ 0
NOASSERTION
TypeScript
Oct 9, 2026
dsh plugin --profile web add dsh-permit-report-checkby PerryLink
?????????(????????????????,?????,???????)
★ 0
NOASSERTION
TypeScript
Oct 8, 2026
dsh plugin --profile web add dsh-bid-qual-checkby PerryLink
???????????(??????????????????????,?????,???????)
★ 0
TypeScript
Oct 8, 2026
dsh plugin --profile web add dsh-lawcite-adapterby ESxyzbil
DSH ??????:?????? + ??????? + ????
★ 1
MIT
JavaScript
Aug 22, 2026
dsh plugin --profile web add dsh-official-document-modeby HERO476
DSH ????(??????):????/????????,???????????????????Selection follow-up for DeepSeek Harness with an independent side-card answerer.
★ 1
MIT
JavaScript
Oct 8, 2026
dsh plugin --profile web add dsh-sidecard-ask