Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39,511
    • Issues 39,511
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,221
    • Merge requests 1,221
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #5934

Closed
Open
Created Apr 19, 2017 by Mark Pundsack@markpundsackContributor

NPM Package Management MVC

Description

We should add API compatible NPM registry support to our artifact repository.

Proposal

For this issue, we will implement the basic core features of the NPM experience:

  1. Some sort of authentication, ideally based on CI_JOB_TOKEN. Authentication can be extended in future releases, but we need to provide some protection on MVC to prevent abuse.
  2. Publish, Download, and List packages.

We will build this into GitLab, rather than trying to integrate a product.

Edited Nov 02, 2018 by Joshua Lambert
Assignee
Assign to
Time tracking