# ENISA Publications Metadata Scraper (`vixendata/enisa-publications-metadata-scraper`) Actor

Monitor official ENISA publication dates, report types, audiences, languages, topics and free original report links. HTML metadata only; no report downloads.

- **URL**: https://apify.com/vixendata/enisa-publications-metadata-scraper.md
- **Developed by:** [Vixendata](https://apify.com/vixendata) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 recognized consultation/publication/alert metadata records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## ENISA Publications Metadata Scraper

Keep an ENISA guidance inventory current without manually copying publication cards. Collect official publication titles, dates, report types, intended audiences, languages, topic labels and original document links for cybersecurity governance and regulatory research workflows.

This is a bounded metadata service for CRA/NIS2 compliance analysts, security governance teams and product-policy researchers. Original publications remain freely available at ENISA. No CVE analysis, compliance conclusions or risk scores are provided.

### Quick start

Run the default input for up to ten records from the first unfiltered catalog page. Or provide an exact publication landing page:

```json
{"discoverRecent":false,"publicationUrls":["https://www.enisa.europa.eu/publications/enisa-secure-by-design-and-default-playbook"],"maxItems":1}
```

Use `publishedSince` (inclusive YYYY-MM-DD) and `topicKeywords` to filter locally. Keywords match official topic labels, not inferred classifications. Explicit URLs are inspected first. A run inspects at most 30 detail pages, returns at most 30 records, and never follows related publications. Zero matches is a valid outcome, not a statement that no relevant publications exist.

### Output

Each default-dataset record contains `source`, canonical `url`, `slug`, `title`, `publishedDate`, `publicationType`, `audiences`, `languages`, `topics`, `agencyDescription` (plain text from the landing-page description), `downloadLinks` (URL and source language), `relatedPublicationUrls`, `additionalResourceLinks`, `sourceStatus`, `observedAt`, `attribution`, `freeSourceNotice`, and `diagnostics`. Missing scalar values are null; missing lists are empty. Publication dates come only from the main publication date, never related-card dates. Source status means a public landing page was retrieved, not legal effectiveness or report currency. Document links are emitted but never fetched.

`RUN_REPORT` in the default key-value store records complete/stopped state, errors, request counts, checked/emitted/filtered counts and documentsFetched=0. Layout mismatches, denied requests and transport failures stop the run and fail the Actor; previously emitted records may remain. Empty results should be checked against this report. No full-archive completeness claim is made.

### Access and scope

Only https://www.enisa.europa.eu/robots.txt, the plain /publications catalog, and strict /publications/slug paths are fetched. No query strings, search, pagination, configurable scraping proxies, redirects, authentication, assets, images, PDFs or downloads. Standard runtime network transport is retained. Requests are sequential, at least two seconds apart, honor applicable robots rules and crawl delays, and stop on HTTP errors including 403/429. Responses are capped at 2 MB; at most 32 requests are normally possible (robots + catalog + 30 details). A source change may require maintenance.

### Attribution and reuse

Source: European Union Agency for Cybersecurity (ENISA), https://www.enisa.europa.eu/publications . ENISA's [legal notice](https://www.enisa.europa.eu/about-enisa/legal-notice), section 1.2, authorizes site-material reproduction with source acknowledgement unless otherwise indicated. Every record retains attribution. No endorsement is implied.

Original publication is freely available from ENISA; this service structures its public publication metadata. Some individual reports have additional terms, including free-access conditions. This Actor does not download, parse, repackage or sell report text/PDFs, logos, photos or third-party assets. Check each original document's terms before reusing its content; no uniform archive commercial license is claimed.

### Product qualification

[Compliance.ai's commercial regulatory-content coverage](https://www.compliance.ai/available-regulatory-content/) explicitly lists EU-ENISA reports, research publications and guidance (Agency_ID 33100017). That supports professional monitoring demand, not proven paying Actor customers. Apify Store searches checked 2026-10-05 found no dedicated ENISA publication inventory. The relevant `garonne/cve-exploited-check` covers CVE exploitation via EUVD, a distinct task. Generic web crawlers can extract pages, but require source-specific work for discovery, typed audience/language/report metadata and main-document versus related-link separation. Store coverage can change.

### Local validation

Python 3.12: `pip install -r requirements.txt`, then `python -m unittest tests -v`. Tests embed compressed original HTML/robots fixtures retrieved 2026-10-05 from the catalog and two cited sample publication pages; no fixture network access is required. Run `python main.py` for the Apify SDK entry point. Production source-access success must be verified separately in the target cloud runtime.

# Actor input Schema

## `publicationUrls` (type: `array`):

Optional explicit HTTPS www.enisa.europa.eu/publications/slug landing pages, maximum 30. No queries, fragments, assets or other hosts.

## `discoverRecent` (type: `boolean`):

Read the first unfiltered official publication catalog page only. No pagination or full archive guarantee.

## `maxItems` (type: `integer`):

Maximum emitted records. At most 30 detail pages inspected even with filters.

## `publishedSince` (type: `string`):

Optional inclusive YYYY-MM-DD local publication-date filter. Missing dates are excluded when set.

## `topicKeywords` (type: `array`):

Optional case-insensitive OR substring matches against official topic labels only, applied locally. Maximum 20 keywords of 100 characters.

## Actor input object example

```json
{
  "publicationUrls": [],
  "discoverRecent": true,
  "maxItems": 10,
  "publishedSince": "",
  "topicKeywords": []
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("vixendata/enisa-publications-metadata-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("vixendata/enisa-publications-metadata-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call vixendata/enisa-publications-metadata-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vixendata/enisa-publications-metadata-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/FkQHTXwh9Lrj3bCg0/builds/HUkpO5Vs13lxC0dL5/openapi.json