Description
I ran an automated link validation process on catalog.json and identified a set of broken or inaccessible external URLs.
The issues include:
- Confirmed HTTP 404 broken links
- Legacy project pages that appear to be no longer maintained
- Deprecated or inaccessible endpoints
Some entries may also reflect migrated projects where updated locations may exist.
Some Examples
Confirmed broken (HTTP 404)
Legacy / inaccessible endpoints
Action Plan
I am opening this issue to document the findings and seek guidance on preferred handling of these cases.
Planned contributions will be proposed as incremental pull requests, focusing on:
- Confirmed HTTP 404 links (safe cleanup candidates)
- Known migrated repositories where official replacements exist
- Gradual review of legacy or deprecated endpoints
Each PR will be scoped to a small, reviewable set of changes grouped by tool or domain.
Request for guidance
According to the repository contribution model (see code.nasa.gov catalog guidelines), deletion or modification of entries is typically handled via pull requests, while legacy or unclear cases may require review.
If there are additional conventions for distinguishing deprecated vs migrated resources in catalog.json, I would appreciate feedback before proceeding further.
Description
I ran an automated link validation process on
catalog.jsonand identified a set of broken or inaccessible external URLs.The issues include:
Some entries may also reflect migrated projects where updated locations may exist.
Some Examples
Confirmed broken (HTTP 404)
Legacy / inaccessible endpoints
Action Plan
I am opening this issue to document the findings and seek guidance on preferred handling of these cases.
Planned contributions will be proposed as incremental pull requests, focusing on:
Each PR will be scoped to a small, reviewable set of changes grouped by tool or domain.
Request for guidance
According to the repository contribution model (see
code.nasa.govcatalog guidelines), deletion or modification of entries is typically handled via pull requests, while legacy or unclear cases may require review.If there are additional conventions for distinguishing deprecated vs migrated resources in
catalog.json, I would appreciate feedback before proceeding further.