Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[CI] Restore comparable dependency-review baseline snapshots

Open
  • Is something wrong?
#3,283 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, java
Domain
ci-cd, databases

Research direction

Start by reviewing the Dependency Review logs and the automatic dependency-submission setup for the ASF repository, then compare its base and head snapshots with the Org runs cited in the issue. An ASF repository administrator is needed to restore comparable snapshots; rerun Dependency Review and verify the missing-base warning is gone and the diff reflects actual dependency changes. Assess the Spring security findings separately, as requested.

Written by the indexing model from the issue text.

Description

Dependency Review on version-upgrade PR #3282 compares a populated head dependency snapshot against an empty base snapshot. It consequently treats existing dependencies as additions and fails on an existing Spring dependency. This is separate from the RPC test failure being repaired in the PR.

Evidence:

  • ASF and Org PR #275 use the same source head and base.
  • ASF dependency-review log reports base snapshots 0, head snapshots 1, and flags spring-webmvc:5.3.27 / GHSA-pc63-qcmh-9cmg.
  • The dependency graph comparison reports all 6,083 ASF entries as added. The Org comparison has 210 added and 209 removed entries and no Spring change; Org dependency-review passes.
  • Spring 5.3.27 already exists in the base POM. Org has successful Automatic Dependency Submission runs for the base commit; no corresponding ASF run was found.

Requested follow-up:

  1. Have an ASF repository administrator inspect the automatic dependency submission setup and restore accurate, comparable snapshots for the base and head using the same detector/build inputs.
  2. Re-run Dependency Review and verify the missing-base warning is gone and the diff represents real dependency changes. A rerun alone cannot populate a missing baseline.
  3. Assess existing Spring/security findings separately. The Spring advisory requires XsltView and particular view mappings; no XsltView configuration was found in the current PD/Store source, but that static check is not a blanket security clearance.

This follow-up does not request a severity downgrade, advisory exemption, fabricated dependency snapshot, new CI framework, or Spring major-version upgrade in the minimal version PR. Current access has push permission but no ASF repository admin role. See GitHub automatic submission setup.

Release tracking: #3242.

Dominant language
Java
Stars
3.2k
Forks
641
Avg merge
2d 9h
Merged PRs (30d)
26

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/hugegraph

All issues in apache/hugegraph

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.