bahmutov / bahmutov/stop-upper

Dependency deprecation warning: nsp (npm)

Open
#37 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
5
Forks
0
PR merge metrics
No merged PRs in 30d

Description

On registry `https://registry.npmjs.org/`, the "latest" version (v3.2.1) of dependency `nsp` has the following deprecation notice:

`The Node Security Platform service is shutting down 9/30 - https://blog.npmjs.org/post/175511531085/the-node-security-platform-service-is-shutting`

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): `package.json`

If you don't care about this, you can close this issue and not be warned about `nsp`'s deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

```
"suppressNotifications": ["deprecationWarningIssues"]
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with package.json and search the project for references to nsp. Determine whether the dependency is still needed and identify the project’s intended response to its deprecation; the work is done when the deprecation warning is addressed without breaking the relevant dependency checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli, tooling
Issue type
Refactor
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.