FGRibreau/check-build

Add Retire.js

Open

#10 opened on Nov 11, 2014

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (695 stars) (33 forks)batch import
enhancementhelp wanted

Description

It seems to me that Retire follows a different approach to identifying modules with vulnerabilities than Nsp does. If this is confirmed, I would support the inclusion of Retire to check-build.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

Tech stack
nodejsjavascript
Domain
securitydeveloper experience
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.
needs investigation
Prerequisites
Node.js developmentfamiliarity with check buildbasic understanding of vulnerability scanning
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue proposes adding Retire.js to check build for vulnerability detection, but it's unclear if Retire.js offers a different approach than existing checks. Investigate Retire.js (http://bekk.github.io/retire.js/) and compare with current Nsp integration. Review check build's architecture in its source code (likely in lib/ or src/ folders). Since the issue is old and unresolved, the maintainer may not have confirmed the need; reach out in the issue comments to clarify the scope and acceptance criteria before proceeding.