3 Commits

Include renames

Author	SHA1	Message	Date
SatoshiQaziMuhammedandClaude Opus 5	d2c8bdefb0	Let the Deno build reach its dependencies, and let its check fail (#8) ... The build rewrites every @pezkuwi import into a deno.land URL, so @pezkuwi/util becomes https://deno.land/x/pezkuwi/util/mod.ts. Upstream can do that because deno.land/x/polkadot is published. Our fork renamed the prefix to x/pezkuwi and never published there: deno.land/x/pezkuwi answers 404, and `deno check` has failed on three modules ever since. Reproduced locally with the same Deno the workflow installs, 2.9.7: TS2307 Cannot find module 'https://deno.land/x/pezkuwi/util/mod.ts' TS2307 Cannot find module 'https://deno.land/x/pezkuwi/util-crypto/mod.ts' TS2307 Cannot find module 'https://deno.land/x/pezkuwi/x-fetch/mod.ts' import_map.in.json is the tooling's own hook for exactly this — pezkuwi-dev-deno-map merges its entries into the generated import_map.json. All three are mapped to npm: specifiers, which Deno resolves natively, at the same version ranges the node build uses. The three packages are already on npm, so nothing new is published and the Deno build now checks against the very code we ship. `yarn deno` exits 0. This deliberately does not decide whether we ever claim deno.land/x/pezkuwi. If we do, the mappings come out again; until then the build works with what we have. The reason none of this was noticed is the second half of the change. The PR job carried continue-on-error from upstream, so its four steps could never turn a pull request red: build had been failing since 2026-09-13 and deno for far longer, and the job reported success throughout. All four pass now — verified locally, lint included, on a clean tree — so the flag is gone and they are gates again. deno.lock joins mod.ts and import_map.json in .gitignore: same check, same kind of generated artifact. package.json carries the key order its own build:before step produces. Gate: scripts/checkDenoMap.mjs, in the Lists workflow so it runs even when the toolchain cannot be installed. Nails: removing the map, bumping a dependency without the map, adding a @pezkuwi dependency with no mapping, and leaving a mapping behind after its dependency goes — each turns it red. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-17 17:16:47 +04:00
SatoshiQaziMuhammedandClaude Opus 5	31b40114a7	Say where this repository actually is (#7) ... * Say where this repository actually is On 2026-04-21 a commit pointed repository, homepage and bugs at our Gitea instance — "migrate git dependencies to Gitea mirror". Nothing else moved. origin is still GitHub, the published @pezkuwi/phishing still says GitHub, and git.pezkuwichain.io/pezkuwichain/phishing answers 500, so everyone who installs the package has been given a dead homepage and a dead bug tracker. It also broke the Master build on 2026-09-13, when the toolchain began reading the field. @pezkuwi/dev, which is ours, does this: const repoPath = pkg.repository.url .split('https://github.com/')[1] .split('.git')[0]; A URL from any other host makes [1] undefined and the build dies with "Cannot read properties of undefined (reading 'split')" — a message that names neither the field nor the file. Three runs failed that way and master has had no green build since. The metadata now says what is true today. This is not a decision about where the project should live: it is an alignment with where the code already is and with what we already publish. That migration is still worth finishing, and this is the sequencing it needs. Moving the repository to Gitea for real means fixing @pezkuwi/dev first, so a toolchain built for a state that hosts its own git stops assuming github.com. scripts/checkRepoMeta.mjs is the tripwire: it fails the metadata here rather than letting it surface as an unreadable stack trace or ship as a dead link. The check runs in the Lists workflow, which has no toolchain to install and so still runs when the build does not. Nails: restoring the April commit turns three cases red, migrating only half the repository turns two red, and leaving homepage behind on the old host turns one red. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Hold the new check to the repository's own lint rules The file I added failed all seven of them and lint had been green: the licence header every file here carries, import order, an optional chain, object keys in ascending order and an argument on its own line. Verified with eslint run the way CI runs it, without --fix. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-17 16:44:00 +04:00
SatoshiQaziMuhammed	767a92904d	Sync the lists with polkadot-js/phishing every day, and publish them with checks (#4) ... * feat: sync the lists with polkadot-js/phishing daily, and check them before publishing The lists had not moved since January 2026, the site that serves them was copied by hand, and the rebrand had turned five real phishing domains into pezkuwichain.* names, unblocking them. - scripts/syncUpstream.mjs and sync-upstream.yml take upstream's lists every day, lay pezkuwi/overlay.json over them, and commit to master. A day out of bounds (too many sites unblocked or added, scam addresses dropped, one of our domains blocked, one of our entries lost) writes nothing and opens an issue. - pezkuwi/overlay.json holds our own entries with their reasons: the five pezkuwichain.* names stay blocked on purpose, and our domains are protected. - scripts/lists.mjs holds the rules; scripts/lists.test.mjs tests them and the sync end to end; scripts/checkLists.mjs checks the committed files, including that they are what sortAll writes. lists.yml runs all three. - pezkuwi/host/ is what phishing.pezkuwichain.io runs: it pulls master hourly and refuses a rewritten history, a blocked own domain, a shrink over 2%, or shards that disagree, with a sandbox test of each refusal. - sortAll strips a trailing dot. Upstream's 817 "scam.xyz." entries were filed under an empty top-level domain in all/all.json, where checkIfDenied never looks; 816 repeated a listed name, and prenads.xyz was blocked nowhere else. - sortAll uses Node's own directory functions instead of @pezkuwi/dev, so the sync and the checks run without installing the build toolchain. - The auto-approve, auto-merge and crosscheck workflows, and the IPFS job, depended on tokens and secrets this repository does not have; removed. The remaining workflows are pinned to commits, with no default permissions and a timeout on every job. * chore(lists): first sync with polkadot-js/phishing Written by scripts/syncUpstream.mjs from upstream bf5e7c6: 658 sites added; nodelinkapp.xyz, org.in and terra-claim.com unblocked by upstream; the five polkadot-js domains the rebrand had renamed blocked again; 816 duplicate "scam.xyz." entries folded into their names and the stray all/all.json gone. 54,051 blocked sites, 279 scam addresses. * fix(lists): commit the .build shard, and refuse a shard git ignores .gitignore held "build/", which also matched all/build/all.json, the shard of the .build top-level domain. Every sort wrote it and no commit held it, so the eight .build scam sites were never published; upstream has the same gap. The directory is excluded from the ignore rule, the shard is committed, and checkLists.mjs now fails on any shard git would ignore (with the old rule restored it does). Also clears the repository's lint on lists.test.mjs: imports sorted, and node:test's describe and it calls marked void. * test(lists): await describe and it, as the repository's lint requires no-floating-promises requires the promises node:test's describe and it return to be handled, and no-void forbids handling them with void. Awaited, the 25 cases run as before.	2026-09-13 17:34:51 +04:00