l3montree-dev / l3montree-dev/devguard

dependency proxy error

Open
#3,008 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/devguard-api
Dominant language
Go
Stars
161
Forks
43
Avg merge
1d 8h
Merged PRs (30d)
37

Description

npm error:

npm warn deprecated intersection-observer@0.10.0: The Intersection Observer polyfill is no longer needed and can safely be removed. Intersection Observer has been Baseline since 2019.
npm error code E404
npm error 404 Not Found - GET https://api.main.devguard.org/chalk/-/chalk-5.6.2.tgz
npm error 404
npm error 404  The requested resource 'https://registry.npmjs.org/chalk/-/chalk-5.6.2.tgz' could not be found or you do not have permission to access it.
npm error 404 This package name is not valid, because 
npm error 404  1. name can only contain URL-friendly characters
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
npm error A complete log of this run can be found in: /Users/larshermges/.npm/_logs/2026-09-02T09_09_32_192Z-debug-0.log

backend log:

2026-09-02T11:09:34+02:00 9:09AM DBG dependencyfirewall/controller.go:125 Fetching from upstream proxy=npm url=https://registry.npmjs.org/sanitize-html bodyPresent=false
2026-09-02T11:09:34+02:00 9:09AM DBG dependencyfirewall/controller.go:125 Fetching from upstream proxy=npm url=https://registry.npmjs.org/next bodyPresent=false
2026-09-02T11:09:34+02:00 9:09AM ERR middlewares/server.go:73 code=404, message=Not Found method=GET path=/chalk/-/chalk-5.6.2.tgz/
2026-09-02T11:09:34+02:00 9:09AM ERR middlewares/server.go:73 code=404, message=Not Found method=GET path=/chalk/-/chalk-5.6.2.tgz/
2026-09-02T11:09:34+02:00 9:09AM INF middlewares/logging_middleware.go:34 handled request method=GET url=/api/v1/dependency-proxy/npm/dompurify/ status=200 duration=75.273575ms

Contributor guide

Open the contributing guide

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.

Research direction

Start at dependencyfirewall/controller.go:125 and inspect the request path through middlewares/server.go:73 for the npm tarball request shown in the logs. Reproduce the chalk 5.6.2 fetch, then verify that the dependency proxy returns the package successfully and that npm install no longer receives the 404 response.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, javascript
Domain
backend, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.