ipfs / ipfs/awesome-ipfs

Eight archived projects are still listed as active; stale.md covers none of them

Open Beginner friendly
#545 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
4.6k
Forks
549
PR merge metrics
No merged PRs in 30d

Description

Eight projects currently listed as active in README.md have had their repositories archived on GitHub, which is the marker for read-only/no-longer-maintained. Per the note in [Stale Projects](./README.md#stale-projects), these belong in [stale.md](./stale.md). Archival status as of 2026-09-18:

Apps:

- [killcord](https://github.com/nomasters/killcord) — archived, last commit 2023-10-11
- [Mintter](https://github.com/MintterHypermedia/mintter) — archived, last commit 2025-01-02
- [Autonomica "IPFS Social Proof"](https://github.com/IBM/ipfs-social-proof) — archived, last commit 2022-02-16

Tools:

- [ipget](https://github.com/ipfs/ipget) — archived, last commit 2026-08-04
- [gomobile-ipfs](https://github.com/ipfs-shipyard/gomobile-ipfs) — archived, repo description reads "[Archived old experiment]", last commit 2026-01-05
- [IPDR](https://github.com/miguelmota/ipdr) — archived, last commit 2024-07-24
- [dScan](https://github.com/p2plabsxyz/dscan) — archived, last commit 2024-02-13
- [wbipfs](https://github.com/wabarc/wbipfs) — archived, last commit 2022-01-16

This follows the resolution in #489, where the outcome was to move stale and inactive projects into `stale.md` rather than drop them, which is what `stale.md` and its "no longer maintained" heading were created for. I checked first: no open issue or pull request currently covers these entries, and `stale.md` contains none of them.

A ninth entry, [solid-ipfs](https://github.com/Eximua/solid-ipfs) under Tools, returns 404 — the repository no longer exists, so there is nothing to move it to.

Two things worth a maintainer's call, since I did not want to guess:

1. `ipfs/ipget` and `ipfs-shipyard/gomobile-ipfs` are under the ipfs org, so archival may reflect an org-level decision rather than the project going quiet. Both are still dead links into archived code, but you may prefer to handle those two differently.
2. The [pull request template](./pull_request_template.md) asks for only one addition, removal, or edit per PR. These are eight separate moves, so I did not bundle them into one PR. If a single sweep PR is preferable, as in 70f9f55, that is fine on my end. Otherwise each move can be submitted on its own.

Happy to open the PRs either way — just say which shape you want.

Contributor guide

Open the contributing guide

Research direction

Read the Stale Projects note in README.md, then compare the Apps and Tools entries in README.md with the corresponding headings in stale.md. Move the eight archived projects into stale.md while preserving their links and categories; leave solid-ipfs out because its repository returns 404. Done means none of the eight remain listed as active and each appears under the appropriate stale.md heading.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.