successor_claim
.com/artifact/com.github.spotbugs/spotbugs) https://javadoc.io/doc/com.github.spotbugs/spotbugs SpotBugs is the spiritual successor of FindBugs, carrying on from the point where it left off with support of its community.
Is spotbugs/spotbugs the successor of findbugsproject/findbugs?
spotbugs/spotbugs subject · successor candidate successor of? findbugsproject/findbugs object · predecessor
spotbugs-findbugs-successor · status observed
Data verified at: 2026-11-10T16:01:02.827Z (UTC)
Conclusion status
No confirmed conclusion exists for this pair. The evidence below is presented for transparency; a relationship conclusion requires a human review that has not happened, or a previous decision no longer matches the current evidence.
Evidence suggests spotbugs/spotbugs may succeed findbugsproject/findbugs (directional claim found). Human review required before publication.
Seed context: Verified 2026-11-03 via GitHub API: spotbugs/spotbugs (ID 72889410) is unarchived and was pushed at 2026-11-03T02:08:39Z; its README calls SpotBugs the spiritual successor of FindBugs and says it carries on with community support. findbugsproject/findbugs (ID 39406013) is unarchived, last pushed 2025-09-27T03:20:02Z; its README says “FindBugs is now SpotBugs” and points project development to SpotBugs. Recorded as successor, not as a GitHub fork. No matching active or retired pair was found by either GitHub ID, locator, or ordered relation. Queue for scheduled collection and human review; this seed is not an approval. Sources: https://github.com/spotbugs/spotbugs/blob/master/README.md#L10 ; https://github.com/findbugsproject/findbugs/blob/master/README.md#L1-L7 ; https://github.com/spotbugs/spotbugs ; https://github.com/findbugsproject/findbugs
Evidence (2)
Verbatim excerpts from official sources, whitespace-normalized. Full payloads are hashed and retained by the pipeline; collection failures never fabricate evidence.
successor_claim
FindBugs is now SpotBugs Old FindBugs site.
Observed repository facts
As of the last verified collection. These are facts about the snapshots, not activity verdicts — a low number is not a claim that a project is inactive.
| Endpoint | Repo | Stars | Last push | Fork | Archived |
|---|---|---|---|---|---|
| spotbugs/spotbugs | spotbugs/spotbugs | 3967 | 2026-11-09T00:08:03Z | no | no |
| findbugsproject/findbugs | findbugsproject/findbugs | 782 | 2025-09-27T03:20:02Z | no | no |
Versions & deployment facts
Official release and package declarations, compared independently of the relationship verdict. These are not installation tests or a migration guarantee. Missing declarations mean unknown.
| spotbugs/spotbugs | findbugsproject/findbugs |
|---|---|
| Unknown: no collected package runtime declaration. | Unknown: no collected package runtime declaration. |
spotbugs/spotbugs
Release-pinned deployment declarations
Release commit · 4.10.5 · complete
Commit: 6816eb256805aa6eed1dced23e6a4aea08cc6660
Collection endpoint (may change) · Observed 2026-11-03T18:01:42.103Z
Response SHA-256: b5b10665fedd4ac1c480e78251c68a0054de3654ce23597413bd70401f774871
Release tree · 4.10.5 · complete
Commit: 6816eb256805aa6eed1dced23e6a4aea08cc6660
Collection endpoint (may change) · Observed 2026-11-03T18:01:42.103Z
File search coverage: selected_manifest_names. Only selected manifest filenames were searched; fixtures and vendored dependency directories are excluded. Unlisted declarations remain unknown.
Response SHA-256: 62077f5a83acc3ac179f5ed466a7dbad4e93262156e8aeffa75a66cf828af4aa
docs/Dockerfile · 4.10.5 · complete
Commit: 6816eb256805aa6eed1dced23e6a4aea08cc6660
Commit-pinned source · Observed 2026-11-03T18:01:42.103Z
File context: unspecified. Package version in file: not declared.
Runtime declaration in this file
Not declared / unknown
Services and dependency roles
No service declarations extracted from this file; production requirements remain unknown.
Container configuration
sphinxdoc/sphinx:8.2.3 · build_base_or_stage · requested platform: unknown. Requested platform is not proof of an available image.
FROM images are build-stage inputs, not proof of a published project image or minimum runtime.
Response SHA-256: f4fb5636105a045d7148ba34e2f7558f76704ae6a371240ca31a13e997c273f6
Container: sphinxdoc/sphinx:8.2.3 · 4.10.5 · complete
Commit: 6816eb256805aa6eed1dced23e6a4aea08cc6660
Collection endpoint (may change) · Observed 2026-11-15T05:01:14.574Z
Observed manifest digest: sha256:8d8bdb4649e6577f20ca9a84ef1e1d46911dc65678fe7908b2e2d3a39508e1c8
image referenced by pinned file; not a proven project release image
Platforms listed in the registry index
- linux/amd64 ·
sha256:d611751f14892bd0681222ead1ac7c990b62acdcf636ecbf092ae6f5e3c0c8c4 - linux/arm64 ·
sha256:e2930d19af773a4315c92cbe336e6a06b28e36cd3bb4d35e2c848166f90dfef3
Registry index descriptors at observation time only, not functional compatibility. Single-image configs are not downloaded; missing platforms remain unknown.
Response SHA-256: 8d8bdb4649e6577f20ca9a84ef1e1d46911dc65678fe7908b2e2d3a39508e1c8
GitHub release · 4.10.5 · complete
GitHub latest published non-prerelease (not a semantic-version ranking). Verified: 2026-11-14T19:02:19.838Z (UTC).
Listed release assets only. Asset names do not prove platform support or successful execution.
- Runtime declarations
Not declared / unknown
- Operating systems
Not declared / unknown
- CPU architectures
Not declared / unknown
- C libraries
Not declared / unknown
Direct dependency declarations
Not declared / unknown
Published artifacts (4)
Provenance
Parser: software-1
First observed: 2026-11-03T15:01:35.904Z (UTC)
Last checked: 2026-11-14T19:02:19.838Z (UTC)
Source response SHA-256: 78af1958fed93d45899d90ddd80e9716a31096511758ae17eb904074773069a4
findbugsproject/findbugs
Release-pinned deployment declarations
Unknown: no release-pinned files have been collected. The default branch is not substituted.
GitHub release · Unknown version · stale evidence
Latest collection: unavailable. No verified release declaration is available. This does not mean the project has no releases or platform support.
Timeline
“Event time” is an upstream timestamp when the source provides one; “first observed” is when this project saw it. They are deliberately separate columns.
| Event | Event time | First observed | Source |
|---|---|---|---|
| spotbugs/spotbugs metadata first observed | — | 2026-11-03T15:01:33.847Z | link |
| recent commit activity of spotbugs/spotbugs observed (5 commits in sampled window) | 2026-11-03T02:07:00Z | 2026-11-03T15:01:34.720Z | link |
| findbugsproject/findbugs metadata first observed | — | 2026-11-03T15:01:35.084Z | link |
| recent commit activity of findbugsproject/findbugs observed (5 commits in sampled window) | 2024-11-28T19:22:07Z | 2026-11-03T15:01:35.902Z | link |
| evidence: successor_claim | — | 2026-11-03T15:01:39.297Z | link |
| automatic evaluation -> needs_review | — | 2026-11-03T15:01:39.298Z | — |
| evidence: successor_claim | — | 2026-11-03T15:01:39.298Z | link |
Decision and dispute history
Review decisions are recorded privately with reasons that stay internal; this public history shows what happened and when, not why.
| Kind | When (UTC) |
|---|---|
| automatic evaluation → needs_review | 2026-11-03T15:01:39.298Z |
To question this report, use the feedback form,
select “data error”, and include pair ID spotbugs-findbugs-successor.
Feedback is reviewed privately and does not change a report automatically.
Snapshot taken at 2026-11-15T10:01:58.857Z (UTC).