What about old packages?

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
git, github
Domain
tooling

Research direction

No files or tests are named in the issue. Start by finding where Healthycode derives package health from repository activity and archive/maintenance signals, then inspect the surrounding docs or tests for the current health policy. Add or update logic for old but stable/archived packages and extend coverage around those cases. Mark it done when old-package handling is explicitly documented and reflected in assertions.

Written by the indexing model from the issue text.

Description

There are some older packages out there:

The point is that activity (on git) may not always correlate well with the health of a package.

Dominant language
Jupyter Notebook
Stars
1
Forks
4
Avg merge
1d 17h
Merged PRs (30d)
4

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 aboutcode-org/healthycode

All issues in aboutcode-org/healthycode

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.