Observation
pg-manual/examples/utils.js:13 hardcodes:
export const PKG_URL = 'https://main.postguard.ihub.ru.nl/pkg'
This is the legacy Radboud iHub PKG deployment. The other three sub-projects all default to the modern staging hostnames:
pg-sveltekit/src/lib/config.ts:5 — https://pkg.staging.postguard.eupg-node/src/config.mjs:4 — https://pkg.staging.postguard.eupg-dotnet/Program.cs:10 — https://pkg.staging.postguard.eu
pg-manual has had this URL since it was first added (commit 64582e1, 2026-04-21) and it survived dep-bump PRs #43 and #50. It is the only file in the repo still pointing at the iHub host.
Question
Is the iHub PKG intentional for pg-manual — e.g. the only deployment that still accepts the irma-demo.gemeente.personalData.* schemes the example uses — or is this an oversight that should track the other examples and move to pkg.staging.postguard.eu?
If the latter, this is a one-line change in utils.js plus a re-run of `npm run dev` to verify the Yivi flow still completes against staging.
If the former, a one-line comment in utils.js explaining the discrepancy would prevent the next audit from re-asking.
Files
pg-manual/examples/utils.js:13
Flagging for maintainer judgement — not dispatching a worker since the correct value depends on deployment intent.
Observation
pg-manual/examples/utils.js:13hardcodes:This is the legacy Radboud iHub PKG deployment. The other three sub-projects all default to the modern staging hostnames:
pg-sveltekit/src/lib/config.ts:5—https://pkg.staging.postguard.eupg-node/src/config.mjs:4—https://pkg.staging.postguard.eupg-dotnet/Program.cs:10—https://pkg.staging.postguard.eupg-manualhas had this URL since it was first added (commit 64582e1, 2026-04-21) and it survived dep-bump PRs #43 and #50. It is the only file in the repo still pointing at the iHub host.Question
Is the iHub PKG intentional for pg-manual — e.g. the only deployment that still accepts the
irma-demo.gemeente.personalData.*schemes the example uses — or is this an oversight that should track the other examples and move topkg.staging.postguard.eu?If the latter, this is a one-line change in
utils.jsplus a re-run of `npm run dev` to verify the Yivi flow still completes against staging.If the former, a one-line comment in
utils.jsexplaining the discrepancy would prevent the next audit from re-asking.Files
pg-manual/examples/utils.js:13Flagging for maintainer judgement — not dispatching a worker since the correct value depends on deployment intent.