-
Notifications
You must be signed in to change notification settings - Fork 1
Update package.json #16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jadoonf
wants to merge
2
commits into
main
Choose a base branch
from
jadoonf-patch-17
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
📊 Package size report 0.8%↑
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
The following behavior was detected in the dependency tree during installation 🛑 3 critical activities detected[email protected]
🛑 This package has inconsistent dependencies in the tarball's package.json
[email protected]
🛑 The name of this package closely resembles other package names ("ini") which are popular on NPM: it might be a typosquatting attempt
[email protected]
🛑 The name of this package closely resembles other package names ("findit2") which are popular on NPM: it might be a typosquatting attempt
|
description: | A package that has an install script in package.json is a potential security risk, as it can be used to execute arbitrary code on the system with the permissions of the user running npm install. This is a common attack vector for malicious packages. |
path: | package.json |
[email protected]
⚠️ install script detected in package.json
- Dependency type
-
Direct dependency
- Metadata
-
description: A package that has an install script in package.json is a potential security risk, as it can be used to execute arbitrary code on the system with the permissions of the user running npm install. This is a common attack vector for malicious packages. path: package.json
🔷 2 low activities detected
[email protected]
🔷 This package version is 0.X.Y: the semver spec mandates those versions for initial development meaning that anything may change at any time and the public API of this package should not be considered stable.
- Dependency type
-
Direct dependency
- Metadata
-
detail: NPM allows changes that do not modify the left-most non-zero element in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >= 0.1.0, and no updates for versions 0.0.X. So, if you depend on ^0.5.21, npm update won't update it to 0.6.0, because only patch updates are allowed. detail_link: https://lstn.dev/semver-parser-node reason: 0.5.21 is less than or equal to 0.x.x-0 spec: https://lstn.dev/semver-spec-0yz
[email protected]
🔷 shady link detected in package
- Dependency type
-
Direct dependency
- Metadata
-
description: A package that contains a link to a shady domain is a potential security risk, as it can be used to exfiltrate sensitive information from the system. A low severity is assigned to this rule as it is not always a security risk, but it is a good practice to avoid those links. path: modules/es.string.link.js
generated by listen.dev
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.