Skip to content

Update dataset card counts - #40

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
update-dataset-card-counts-30801903493
Open

Update dataset card counts#40
github-actions[bot] wants to merge 1 commit into
mainfrom
update-dataset-card-counts-30801903493

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Automated update of triple counts and date in the HuggingFace dataset card.

Summary by Sourcery

Update the Hugging Face dataset package metadata and documentation to reflect the latest snapshot of all integrated security data sources.

Enhancements:

  • Regenerate dataset metadata, statistics, and neighborhood graph files to align with the latest ingestion, including newly added CVE, CWE, and CPE entities.

Documentation:

  • Refresh the dataset card with the new last-updated timestamp and revised record counts for each source table.

@sourcery-ai

sourcery-ai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Automated refresh of the HuggingFace dataset card, metadata, statistics, and neighborhoods to reflect a new security knowledge graph snapshot with updated per-source record counts.

Flow diagram for updating HuggingFace dataset snapshot metadata

flowchart TD
    A[New_security_KG_snapshot] --> B[Regenerate_.stats_JSON]
    A --> C[Regenerate_.neighborhoods_JSON]
    B --> D[Update_.metadata_JSON]
    C --> D
    D --> E[Update_README_counts_and_timestamp]
Loading

File-Level Changes

Change Details Files
Update dataset card documentation to reflect latest snapshot date and per-source record counts.
  • Bump the dataset card "Last updated" timestamp to the new snapshot time.
  • Adjust per-source record counts in the README table for CVE, CPE, EPSS, KEV, Vulnrichment, GHSA, Sigma, ExploitDB, MISP Galaxy, LOLBAS, LOLDrivers, Atomic, Nuclei, EUVD, OSV, and combined rows to match regenerated stats.
hf_dataset/README.md
Regenerate dataset-level metadata, conversion report, statistics, and neighborhoods for the new snapshot.
  • Rewrite conversion report JSON with the latest ingestion and transformation summary.
  • Refresh dataset metadata JSON (e.g., feature schemas, splits, sizes, or checksums) to align with the new graph snapshot.
  • Regenerate per-source statistics JSON files under .stats (counts and related metrics) for all sources, including combined.
  • Regenerate neighborhood JSONs for impacted CVEs, CWEs, GHSAs, ATT&CK techniques, and CPEs to include new entities and relationships.
  • Add neighborhood JSONs for new CVEs, CWEs, and Red Hat / Microsoft CPE products introduced in this snapshot.
  • Update neighborhoods index JSON to reference the newly generated neighborhood files.
hf_dataset/.conversion_report.json
hf_dataset/.metadata.json
hf_dataset/.neighborhoods/0f59ce3b-20ac-41ba-8010-2abc74827eb8.json
hf_dataset/.neighborhoods/87752fb8-e9f6-4235-91e2-c4343677d817.json
hf_dataset/.neighborhoods/CVE-*.json
hf_dataset/.neighborhoods/CWE-*.json
hf_dataset/.neighborhoods/GHSA-*.json
hf_dataset/.neighborhoods/T*.json
hf_dataset/.neighborhoods/cpe_*.json
hf_dataset/.neighborhoods/index.json
hf_dataset/.stats/*.stats.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We encountered an error and are unable to review this PR. We have been notified and are working to fix it.

You can try again by commenting this pull request with @sourcery-ai review, or contact us for help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants