Search results
1944 packages found
It's a library that allows us to test api endpoints by fuzzing them with malicious payloads that you can choose. It bases on `supertest` package.
Jfrog Curation dummy malicious package
This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, Emallates is hanging on to the package name, but loosely, and we'll probably give it to you if you want it.
This package has been claimed by Synack to serve as a Proof of Concept. Non-malicious code uploaded for test purposes only.
This package has been claimed by Synack to serve as a Proof of Concept. Non-malicious code uploaded for test purposes only to serve as a Proof of Concept.
This package is a proof of concept used by Kaiksi to conduct security research. It has been uploaded for test purposes only. Its only function is to confirm the installation of the package on a victim's machines. The code is not malicious in any way and w
This package allows you to verify any link through the google safe browsing
Introducing the Captcha Generator, an efficient npm package that provides a simple and secure solution for generating captcha codes. This versatile package utilizes popular keywords such as randomization, security, and verification to create unique and cu
- Captcha
- Generator
- npm
- package
- randomization
- security
- verification
- unique
- codes
- customizable
- length
- integration
- web
- applications
- View more
To avoid malicious use Amesio is holding on to this package name.
This package helps to filter the input text that is malicious and intended to attack the server.
- xss detection
- xss filter
- input sanitization
- network security
- attack
- machine learning
- bayes-classifier
- cyber security
- xss
- xss attack
- xss attack prevention
- network attack
No malicious. Just a package for POC of dependency confusion.
Package to catch insecure invocations of 'npm ci', when a malicious script has a chance to steal your secret environment variables
This package is no longer supported and has been deprecated. To avoid malicious use, npm is hanging on to the package name.
This package name is not currently in use, but was formerly occupied by another package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it.