Holding package. This name belongs to Palveron and is held only so that nobody else can claim it. It will never carry functionality.
This is a holding package. This name belongs to Palveron and is held only so that nobody else can claim it. It will never carry functionality.
Running it prints a message to stderr and exits with code 1. Nothing else happens.
The help output and documentation of @palveron/agent-shield version 0.1.0 showed commands of the form "npx palveron shield init". That form was wrong: "palveron" is the bin inside @palveron/agent-shield, not a package of its own, so npx asks the registry for a package called "palveron", and until now no such package existed.
Install the real package and run the real command:
npm install -g @palveron/agent-shield
palveron shield init
Without a global install, the -p flag points npx at the right package:
npx -p @palveron/agent-shield palveron shield init
Documentation: https://docs.palveron.com
Source of this holding package: https://github.com/palveron/npm-name-locks
FAQs
Holding package. This name belongs to Palveron and is held only so that nobody else can claim it. It will never carry functionality.
We found that palveron demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Company News
Socket is joining the OpenJS Security Stewardship Program to fund Node.js vulnerability research, maintainer remediation, and security releases.
Security News
Two compromised GitHub Actions were re-enabled with malicious tags intact, exposing thousands of downstream repositories to Mini Shai-Hulud.
Research
/Security News
A malicious Firefox extension fetches its payload after installation to evade detection, steal Google session cookies, and automate account takeover.