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

add version number for each repo

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, nodejs
Domain
api, backend

Research direction

Start at the / endpoint that builds the repository JSON response and trace how repository data is fetched and cached. Use the latest GitHub release tag for each repository as the release value, then verify that every returned repository includes the field in the documented response shape.

Written by the indexing model from the issue text.

Description

Currently only the bigchaindb/bigchaindb repo gets a version number in its json response.

Scope

Include version number based on the latest GitHub release tag for each repo as value of a release key in the / endpoint. Like so:

[
  {
    "name": "project-name",
    "description": "The description",
    "stars": 3040,
    "forks": 293,
    "is_fork": false,
    "release": "v0.10.0",
    "url": "https://github.com/bigchaindb/project"
  }
]

Needed for solving https://github.com/ascribe/bigchain-website/issues/139

Dominant language
JavaScript
Stars
7
Forks
9
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.