**[BUG] `npx kshield@1.1.0 init` fails with `ETARGET` – No matching version found on npm**

[LohithCoders]

Description

Attempting to initialize KShield using the npm installation flow fails because npm is unable to resolve the requested package version (1.1.0). As a result, the installation terminates before the postinstall script is executed.

This blocks verification of the npm installation path for v1.1.0, including the automatic download of the platform-specific binary from the GitHub Release.

---

Steps to Reproduce

1. Open a terminal in a clean environment.

2. Create a new scratch repository:

   mkdir kshield-test
   cd kshield-test
   git init

3. Run:

   npx kshield@1.1.0 init

---

Expected Behavior

• npm should resolve and download kshield@1.1.0.
• The postinstall script should execute.
• The correct platform-specific binary should be downloaded from the v1.1.0 GitHub Release.
• KShield should initialize successfully.

---

Actual Behavior

npm fails before the installation begins with the following error:

npm ERR! code ETARGET
npm ERR! notarget No matching version found for kshield@1.1.0.
npm ERR! notarget In most cases you or one of your dependencies are requesting a package version that doesn't exist.

Since the package cannot be resolved, the postinstall script is never executed.

---

Impact

• Blocks the npm installation flow for v1.1.0.
• Prevents verification of the automatic platform binary download.
• Prevents end-to-end validation of the npm installation path as described in the v1.1.0 release verification checklist.

---

Environment

• OS: Windows 10

• Package Manager: npm / npx

• Command Executed:

  npx kshield@1.1.0 init

---

Notes

This issue appears to be related to the availability or publication of the kshield@1.1.0 package on the npm registry. Since the package cannot be resolved, the installation process does not reach the postinstall stage required to download the platform-specific binary.