-
Notifications
You must be signed in to change notification settings - Fork 68
Description
I am opening this issue to formally request the transfer of ownership for the virtual-select-plugin package on npm.
Background
As the primary contributor managing the releases and maintenance of the virtual-select project for the past year, I have run into a critical blocker. The current npm automation tokens have expired, and because I do not have administrative access to the npm package, I am unable to publish new versions, security patches, or bug fixes.
Why is this necessary
Maintenance Continuity: There has been no activity from the original owner account on GitHub or npm for over 12 months.
Security Risk: We cannot patch vulnerabilities or update dependencies in the published npm package, leaving users at risk.
Community Support: I am currently the person triaging issues and merging PRs, but the community is not receiving these updates via the registry.
Proposed Action
I am requesting that you add my npm username ([Your NPM Username]) as an owner of the package or transfer the package entirely so that I can resume the release cycle.
Note to npm Support: If there is no response to this issue within 72 hours, I will be providing this link as evidence of an abandoned package dispute to the npm Registry Team to make sure the continued safety and maintenance of the project is maintained.
If the owner, @sa-si-dev, suddenly reappears, he doesn't have to give up full control. He can simply run: npm owner add gnbm virtual-select-plugin