Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,955
    • Issues 35,955
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,281
    • Merge Requests 1,281
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #13762

Closed
Open
Opened Aug 23, 2019 by Tim Rizzi@trizziDeveloper

Dependency graph for the NPM Registry

Problem to solve

The GitLab NPM Registry allows node.js developers to build, publish and share their packages to GitLab, alongside their source code and CI/CD pipelines. However, we do not offer any visualization of the dependency graph to allow users to clearly understand the impact one component has on another.

Intended users

  • Software Developer
  • DevOps Engineer
  • Systems Administrator
  • Security Analyst

Further details

Proposal

Add a dependency graph to the NPM Registry.

Edited Aug 23, 2019 by Tim Rizzi
Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#13762