Proconip

Latest version: v1.4.7

Safety actively analyzes 723976 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 9

0.2.5

One more Last 'last' try publishing to the github node package repo

0.2.4

Again, this update has absolutely no functional changes to the library since the v0.2.0 release. It was just created to fix the release workflow(s).

0.2.3

Again, this update has absolutely no functional changes to the library since the v0.2.0 release. It was just created to fix the release workflow(s).

0.2.2

This update has absolutely no functional changes to the library since the 0.2.0 release. It was just created to fix the release workflow(s).

0.2.1

This is because the first release workflow run after switching to an unscoped
package name unnecessarily failed due to an error stating that
'https://registry.npmjs.org/procon-ip' was not found while publishing to the
github repo. Actually, it was already successfully published to npmjs at that
moment. But maybe not yet reachable via registry api.
Finally in turn the re-run obviously failed in publishing to npmjs, because
the package/version already exists.
I thought about unpublishing the packages and re-run the workflow again. But
this might end in the same situation because the package might be removed
completely from npmjs, after the only existing version has been unpublished.

0.2.0

Page 8 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.