@lxo-blocks/react
Advanced tools
Comparing version 0.0.1-security to 0.0.1
{ | ||
"name": "@lxo-blocks/react", | ||
"version": "0.0.1-security", | ||
"version": "0.0.1", | ||
"description": "security holding package", | ||
"repository": "npm/security-holder" | ||
"publishConfig": { | ||
"registry": "https://registry.npmjs.org/" | ||
} | ||
} |
# Security holding package | ||
This package contained malicious code and was removed from the registry by the npm security team. A placeholder was published to ensure users are not affected in the future. | ||
This package once was published byu an unauthorized entity and used to contain malicious code. | ||
Please refer to www.npmjs.com/advisories?search=%40lxo-blocks%2Freact for more information. | ||
It therefore was removed from the registry by the npm security team and ownership was restored. | ||
A placeholder was published to ensure users are not affected in the future. |
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
No repository
Supply chain riskPackage does not have a linked source code repository. Without this field, a package will have no reference to the location of the source code use to generate the package.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
471
8