Scan package.json from github/gitlab repo

Description

Contributor guide

Tech stack

javascriptnodejs

Domain

frontendapi

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

npm or yarnbasic Node.js

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60

Research direction

The issue requests adding a feature to scan package.json from a GitHub or GitLab URL. The repository is bundlephobia, a JavaScript tool that analyzes npm package sizes. To implement, you would need to add a text input for URLs, fetch the raw package.json from the remote repository using the GitHub/GitLab API (e.g., raw.githubusercontent.com or GitLab's raw endpoint), parse it, and then run the existing analysis. Look at the current scanner implementation in the repository (likely in a file like src/scan.js or similar) to understand how package.json is processed. Also consider handling authentication for private repos, network errors, and user feedback.