PeerCortex/package.json
Rene Fichtmueller ceb49d0ab6 merge: reconcile prod-snapshot-2026-07-16 into main
Merges the production-only changes (Izzy PDF export via puppeteer,
Adoption Tracker overlay, audit scripts, deploy/utility scripts) that
had been living as uncommitted edits directly on Erik since before the
2026-07-14 backend refactor, on top of current main.

4 real conflicts, resolved by keeping whichever side is actually
functional rather than picking a side mechanically:

- package.json / package-lock.json: trivial union, kept both the
  refactor's pg/playwright deps and the snapshot's puppeteer dep;
  lockfile regenerated via `npm install --package-lock-only` rather
  than hand-edited
- server.js top-of-file: additive, kept both the localDb require
  (backend refactor) and the puppeteer lazy-loader (PDF export)
- server.js /api/health aspa_adoption block: main referenced
  `aspaAdoptionHistory`, a variable that is never declared anywhere
  in this file (confirmed by grep) -- a pre-existing dead reference
  that would throw if this code path ever ran. Kept the snapshot's
  working `aspaAdoptionDailyHistory`/`roaStore.count` version, which
  matches the live /api/health output from production. Also fixed
  the identical bug in the neighboring .catch() fallback block a few
  lines down (same undefined variable, not part of the conflict
  itself -- pre-existing on main, same fix applied for consistency).
- server.js hijack-subscribe/webhooks section (186 lines): main's
  side was just a 2-line comment ("Migrated to
  src/features/hijack-subscribe/"). Kept the snapshot's actual
  working implementation instead, because server.js does not
  require() or import anything from src/features/ or dist/ anywhere
  -- confirmed by grep. The "migration" only ever happened on the
  src/features/ side; server.js's own HTTP routing was never wired
  up to call into it.

IMPORTANT CAVEAT, found while investigating the above and NOT fixed
here: server.js still has 13 other "// Migrated to src/features/..."
comments (bgp-communities, irr-audit, asset-expand, rpki-history,
aspath, looking-glass, ix-matrix, submarine-cables, global-infra,
hijack-alerts (Fastify), changelog, rib, prefix-changes) where the
same thing is true -- the route implementation was deleted from
server.js and never replaced with a working call into src/features/.
These weren't touched by this merge (git didn't flag them as
conflicts, because production's snapshot never touched those
sections either -- only main changed them, by deleting them). If
this server.js is ever deployed as the new production file as-is,
those 13 endpoints will silently 404 or fall through, exactly like
the hijack-subscribe one would have if I'd taken main's side. This
is a pre-existing gap in the 2026-07-14 refactor (PR #1), unrelated
to the Izzy/Adoption Tracker work, and needs a deliberate decision
(wire server.js to src/features/, or confirm those routes are meant
to live on a different process/port entirely) before this branch
should be treated as deployable.

`node --check server.js` passes. Not deployed to Erik as part of
this commit -- Erik's currently-live server.js/public/index.html
are untouched.
2026-07-16 08:54:48 +02:00

98 lines
2.5 KiB
JSON

{
"name": "peercortex",
"version": "0.7.0",
"description": "AI-Powered Network Intelligence Platform — MCP Server for PeeringDB, RIPE Stat, BGP analysis, RPKI monitoring, and peering automation. Powered by local Ollama.",
"main": "dist/mcp-server/index.js",
"types": "dist/mcp-server/index.d.ts",
"bin": {
"peercortex": "dist/mcp-server/index.js"
},
"scripts": {
"build": "tsc",
"dev": "tsx watch src/mcp-server/index.ts",
"start": "node dist/mcp-server/index.js",
"lint": "eslint src/",
"lint:fix": "eslint src/ --fix",
"typecheck": "tsc --noEmit",
"test": "vitest run",
"test:watch": "vitest",
"test:coverage": "vitest run --coverage",
"clean": "rm -rf dist/",
"prepublishOnly": "npm run build"
},
"keywords": [
"mcp",
"mcp-server",
"peeringdb",
"bgp",
"rpki",
"ripe-stat",
"network-intelligence",
"peering",
"asn-lookup",
"prefix-lookup",
"internet-exchange",
"route-leak-detection",
"bgp-hijack-detection",
"bgp-monitoring",
"bgp-analysis",
"peering-automation",
"rpki-monitoring",
"rpki-compliance",
"noc-tools",
"network-operator",
"ollama",
"self-hosted",
"local-ai",
"claude-code",
"irr-query",
"route-views",
"bgp-anomaly"
],
"author": "Rene Fichtmueller",
"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/renefichtmueller/PeerCortex.git"
},
"bugs": {
"url": "https://github.com/renefichtmueller/PeerCortex/issues"
},
"homepage": "https://peercortex.org",
"engines": {
"node": ">=20.0.0"
},
"dependencies": {
"@grpc/grpc-js": "^1.14.3",
"@grpc/proto-loader": "^0.8.0",
"@modelcontextprotocol/sdk": "^1.12.0",
"axios": "^1.6.0",
"better-sqlite3": "^11.7.0",
"cheerio": "^1.0.0",
"fastify": "^5.8.5",
"joi": "^17.11.0",
"node-cron": "^3.0.3",
"node-whois": "^2.1.3",
"ollama": "^0.5.12",
"pg": "^8.11.0",
"playwright": "^1.40.0",
"puppeteer": "^24.42.0",
"zod": "^3.24.0"
},
"devDependencies": {
"@playwright/test": "^1.40.0",
"@types/better-sqlite3": "^7.6.12",
"@types/node": "^22.10.0",
"@types/node-cron": "^3.0.0",
"@types/pg": "^8.11.0",
"@typescript-eslint/eslint-plugin": "^8.18.0",
"@typescript-eslint/parser": "^8.18.0",
"@vitest/coverage-v8": "^2.1.0",
"eslint": "^9.16.0",
"nock": "^13.4.0",
"tsx": "^4.19.0",
"typescript": "^5.7.0",
"vitest": "^2.1.0"
}
}