Durham Planning Properties and Details Scraper

This Actor is disabled for source requests by default. Durham County Council's linked copyright notice restricts copying and distribution without written permission, and no reuse license covering this Actor's extraction and dataset use is recorded. Do not enable collection unless you hold written permission covering automated collection, storage, and intended use. The authorization input is an attestation, not permission. This Actor collects planning-application records, not property-sale or rental listings.

Example input:

{
  "authorizationConfirmed": false,
  "mode": "search",
  "keyword": "",
  "caseStatus": "",
  "maxItems": 10
}

When written permission is in place, the search mode accepts a keyword, reference, postcode, or address and optionally filters Current or Decided applications. query is supported as an alias for keyword. maxItems is bounded to 1–20 and stops pagination/enrichment promptly. Each record includes a stable application key, reference, proposal, status, address, public detail/canonical URL, available dates and decision fields, document count, and extraction timestamp; unavailable optional portal fields are omitted.

The Actor uses the portal's public simple-search form and detail pages only after the authorization gate is satisfied. It does not log in or access private case information. With the default authorization setting, it reports SUCCEEDED / SKIPPED_POLICY in the OUTPUT summary, makes zero source requests, and writes no dataset rows.

Clean completion, including an empty search or no-query run, is SUCCEEDED / COMPLETED. A source or storage failure after one or more application rows are saved is SUCCEEDED / PARTIAL. A failure with no saved application rows is FAILED / FAILED. The dataset contains planning-application records only; bounded failure details and counts are kept in the aggregate OUTPUT summary. Only FAILED exits non-zero.

Offline validation:

node --check src/main.js
apify validate-schema

Dependency security and HTTP caching

The locked dependencies require Node.js 20.18.1 or later. Implemented Actor Cloud builds use Node.js 22.

HTTP response caching is disabled throughout the SDK dependency graph by a project-owned, tested non-caching policy replacement. Responses are always fetched afresh; stale cached responses and serialized cache headers cannot be reused. This replaces the vulnerable package rather than suppressing its advisory. The locked FTP client is 6.2.1; the SDK keeps its supported interface.

The original unpatched-cache advisory is GHSA-ch52-4w7c-c8xp. The FTP patch is documented in GHSA-c475-qrg2-pj4r. Project tests include actual localhost HTTP requests with a shared cache and distinct user headers. These tests make no target-site requests and do not qualify extraction.