Skip to content

docs: state which script regions gdp-proof-producer checks #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BartWaardenburg merged 1 commit into from
Oct 6, 2026
Merged

docs: state which script regions gdp-proof-producer checks #89

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion explanations/dead-code.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -485,7 +485,9 @@ The `rules."policy-violation"` master setting defaults to `warn`. A per-rule `se

The opt-in `gdp-proof-producer` rule follows calls to `@gdp-ts/core.defineProof` through the module graph. It reports factory creation outside the rule's `allowedFiles`. With `proofKinds`, you can require a specific literal proof label to be created only in its owner file. Configure both rules in a [rule pack](/configuration/overview#config-fields).

Fallow recognizes direct, renamed, and namespace imports, including unambiguous re-exports through project modules and workspace packages. A locally shadowed import name does not match. Each call site gets its own finding, with the resolved factory and a static proof label when available. This rule also checks analyzed files unreachable from entry points.
Fallow recognizes direct, renamed, and namespace imports, including unambiguous re-exports through project modules and workspace packages. A locally shadowed import name does not match. Each recognized call site gets its own finding, with the resolved factory and a static proof label when available. This rule also checks analyzed files unreachable from entry points.

The rule checks JavaScript and TypeScript source, including JSX expressions, Vue and Svelte script blocks, Astro frontmatter, and MDX module statements. It does not check calls in Vue, Svelte, Astro, or MDX template expressions, or in Astro inline client scripts.

Move the factory to an allowed authorization module and expose an operation that performs the permission check. Retain the gdp-ts ESLint or Oxlint rules, including `no-exported-prover`, and your TypeScript checks. Restricting factory locations does not prevent an allowed module from exporting a prover that callers can invoke without authorization.

Expand Down
6 changes: 3 additions & 3 deletions public-content-manifest.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
"visibility": "public-only"
},
"content": {
"sha256": "8e95c54d440d2281ae6fd8ecabd36a66e163818f824b7385b859448d20fdcd09",
"sha256": "438916731ae5721947f6a9bfc2c7a0d72b431830d4cf3a59c6dd6d977815568a",
"files": [
{
"path": "adoption.mdx",
Expand Down Expand Up @@ -291,8 +291,8 @@
},
{
"path": "explanations/dead-code.mdx",
"bytes": 92939,
"sha256": "59a88315d81e3195613a30e2944b65e4823e783583ef8846efdfe5daab60c91c"
"bytes": 93215,
"sha256": "8e557f7ac7f2bdcf232a59821c19e991b80f15dfa739a28804b5297a2f54534f"
},
{
"path": "explanations/duplication.mdx",
Expand Down