sitespeedio / sitespeedio/sitespeed.io
node-static package is vulnerable,How to bypass this dependency
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5k
- Forks
- 624
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
Your question
node-static is dependent package for sitespeed /browsertime. But node-static is considered highly vulnerable, and our organization is not allowing us to download this dependency. Please refer the package health score from the URL below.
and Due to this we are not able to install it via NPM install command. Refer the exception . Is there a way to bypass the dependency and proceed.
X:>npm install -g sitespeed.io@35.2.0
npm error code E404
npm error 404 Not Found - GET https://XXX-nprepo.XXX.com/artifactory/api/npm/fm-npm-auto-local/node-static
npm error 404
npm error 404 'node-static@^0.7.11' is not in this registry.
npm error 404
npm error 404 Note that you can also install from a
npm error 404 tarball, folder, http url, or git url.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no repository files or tests; start by reproducing npm install -g sitespeed.io@35.2.0 against the stated registry and inspect the dependency tree for node-static@^0.7.11. Done means establishing whether the dependency is removable or replaceable, or documenting the supported installation path when the registry blocks it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100