Dependency deprecation warning: nsp (npm)
- Dominant language
- JavaScript
- Stars
- 0
- 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, the affected file named in the report, and check how nsp is used by the project. Determine whether the deprecated dependency still has a role and verify the existing test command; done means the deprecation warning is addressed or the issue is explicitly closed as unnecessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100