pre-post-token-vulnerability

v0.0.4

This package is intended to demonstrate the leaking of secrets using pre- and postevent data. For more information about how to use this package see README

Latest version published 1 year ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

This is a malicious package

pre-post-token-vulnerability is a malicious package. The package's name is based on existing repositories, namespaces, or components used by popular companies in an effort to trick employees into downloading it, also known as 'dependency confusion'. Therefore, you're only vulnerable if this package was installed from the public NPM registry rather than your private registry. This malicious package was uncovered by one of Snyk's automated algorithms, and was confirmed to contain malicious code by our Security Research Team. For more context, please visit our .

Security

Security issues found
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
0.0.4 | 08/2021
Popular
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (1)

Download trend
Dependents
0
GitHub Stars
0
Forks
0
Contributors
1

Direct Usage Popularity


The npm package pre-post-token-vulnerability receives a total of 1 downloads a week. As such, we scored pre-post-token-vulnerability popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package pre-post-token-vulnerability, we found that it has been starred ? times, and that 0 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
1
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like pre-post-token-vulnerability is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 28/100 package health 28/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
1 year ago
Last Commit
1 year ago

Further analysis of the maintenance status of pre-post-token-vulnerability based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for pre-post-token-vulnerability is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
not defined

Age
1 year
Dependencies
1 Direct
Versions
5
Install Size
1.16 kB
Dist-tags
1
# of Files
3
Maintainers
1
TS Typings
No

pre-post-token-vulnerability has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.