issues
search
RafaelGSS
/
is-my-node-vulnerable
package that checks if your Node.js installation is vulnerable to known security vulnerabilities
MIT License
174
stars
6
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
feat: add support to old versions of Node.js
#23
RafaelGSS
opened
22 hours ago
0
Move action to a different package, and call `is-my-node-vulnerable` API from it.
#22
trivikr
opened
2 days ago
0
Specify minimum supported Node.js version in package.json engines field
#21
trivikr
opened
2 days ago
2
Replace undici with native https.request
#20
trivikr
opened
3 days ago
0
Use native options of dependencies when available
#19
trivikr
opened
3 days ago
4
feat: display cve severity on reporter
#18
RafaelGSS
closed
1 month ago
0
test: add BadBatchBug check
#17
RafaelGSS
closed
3 months ago
0
Bump node to v20
#16
theboolean
closed
5 months ago
0
Update node version in action.yml: v16 -> v18
#15
theboolean
closed
5 months ago
0
feat: added platform validation
#12
UlisesGascon
closed
1 year ago
3
Add Github Action capabilities
#11
UlisesGascon
closed
1 year ago
0
test: add latest release to test
#10
RafaelGSS
closed
1 year ago
0
Add support to environment check
#9
RafaelGSS
closed
1 year ago
3
feat: add end-of-life support
#8
RafaelGSS
closed
1 year ago
0
chore: add v12 to ci
#7
srl295
closed
1 year ago
0
fix: drop required node to <=14.0.0
#6
srl295
closed
1 year ago
3
feat: warn if not an actively supported Node.js version
#5
srl295
closed
1 year ago
22
chore: add repository field to package.json
#4
srl295
closed
1 year ago
0
[Fix] drop required node to 12
#3
ljharb
closed
1 year ago
6
bug: needs a minimum version check
#2
srl295
closed
1 year ago
22
Error: connect ECONNREFUSED 0.0.0.0:443
#1
tjx666
closed
1 year ago
2