requestshield 0.1.6 → 0.1.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -4,7 +4,7 @@ Customer-facing CLI for IntelliFend RequestShield. It allows customers to sign
4
4
  in, manage applications and their credentials, install the RequestShield Skill
5
5
  for Codex or Claude, and update an npm-installed CLI.
6
6
 
7
- Current package version: `0.1.6`.
7
+ Current package version: `0.1.5`.
8
8
 
9
9
  ## Requirements
10
10
 
@@ -259,7 +259,7 @@ the working directory or require a staged packaging copy.
259
259
  requestshield update check
260
260
  ```
261
261
 
262
- Checks the npm registry for the latest `requestshield` version.
262
+ Checks the npm registry for the latest `@intellifend/requestshield` version.
263
263
  When a newer version exists, the CLI displays the current and latest versions
264
264
  and asks:
265
265
 
@@ -270,7 +270,7 @@ Install RequestShield <version> globally with npm? (y/N):
270
270
  Entering `y` runs the equivalent of:
271
271
 
272
272
  ```console
273
- npm install --global requestshield@<latest-version>
273
+ npm install --global @intellifend/requestshield@<latest-version>
274
274
  ```
275
275
 
276
276
  This command requires an interactive terminal, Node.js, and npm. It updates a
@@ -283,7 +283,7 @@ returns without querying the registry, prompting or installing anything.
283
283
  Install globally:
284
284
 
285
285
  ```console
286
- npm install --global requestshield
286
+ npm install --global @intellifend/requestshield
287
287
  requestshield --help
288
288
  requestshield --version
289
289
  ```
@@ -296,14 +296,14 @@ versions already published.
296
296
  Run a specific version without installing globally:
297
297
 
298
298
  ```console
299
- npx --yes --package=requestshield@0.1.6 requestshield --help
300
- npx --yes --package=requestshield@0.1.6 requestshield signin
299
+ npx --yes --package=@intellifend/requestshield@0.1.5 requestshield --help
300
+ npx --yes --package=@intellifend/requestshield@0.1.5 requestshield signin
301
301
  ```
302
302
 
303
303
  To invoke the update command through npx, include the package name:
304
304
 
305
305
  ```console
306
- npx --yes --package=requestshield@0.1.6 requestshield update check
306
+ npx --yes --package=@intellifend/requestshield@0.1.5 requestshield update check
307
307
  ```
308
308
 
309
309
  Do not run `npx update check`; npm interprets `update` as the name of a different
@@ -496,7 +496,7 @@ npm pack ./build --dry-run
496
496
  npm pack ./build --pack-destination ./build
497
497
  ```
498
498
 
499
- The latter writes `build/requestshield-<version>.tgz`. Archives are
499
+ The latter writes `build/intellifend-requestshield-<version>.tgz`. Archives are
500
500
  generated artifacts, ignored by Git, and are not required in source control or
501
501
  before publishing. The package listing should contain `src/main.mjs`,
502
502
  `config/.env.prod` and the complete Skill, with no QAT/STG configuration or
@@ -534,7 +534,7 @@ root and publish from this source package. Store a `.tgz` as a CI artifact only
534
534
  when the release workflow needs a separately retained archive.
535
535
 
536
536
  ```console
537
- npm view requestshield version
537
+ npm view @intellifend/requestshield version
538
538
  npm run check
539
539
  npm pack --dry-run
540
540
  npm publish --access public
@@ -543,9 +543,9 @@ npm publish --access public
543
543
  Verify the published package:
544
544
 
545
545
  ```console
546
- npm view requestshield version
547
- npm dist-tag ls requestshield
548
- npx --yes --package=requestshield@0.1.6 requestshield --version
546
+ npm view @intellifend/requestshield version
547
+ npm dist-tag ls @intellifend/requestshield
548
+ npx --yes --package=@intellifend/requestshield@0.1.5 requestshield --version
549
549
  ```
550
550
 
551
551
  ## Management API contract
package/config/.env.prod CHANGED
@@ -1,7 +1,5 @@
1
- # Public production settings shipped in the npm package. Never add secrets.
2
- API_URL=https://api.intellifend.ai
3
- # Fill in the production Connected App values before releasing sign-in.
4
- OAUTH_ISSUER=
5
- # Optional callback iss pin; blank uses OAUTH_ISSUER.
6
- OAUTH_AUTHORIZATION_ISSUER=
7
- OAUTH_CLIENT_ID=
1
+ # Public QAT settings for source-checkout development only. Never add secrets.
2
+ API_URL=https://management-api-qat.intellifend.ai
3
+ OAUTH_ISSUER=https://incongruous-cherry-0283.customers.stytch.dev
4
+ OAUTH_AUTHORIZATION_ISSUER=stytch.com/project-test-968146e2-6f34-4936-9d1c-a7e966813c70
5
+ OAUTH_CLIENT_ID=connected-app-test-5ff62ca4-c0eb-48c3-84e5-06ae8f669998
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "requestshield",
3
- "version": "0.1.6",
3
+ "version": "0.1.7",
4
4
  "description": "Customer CLI for IntelliFend RequestShield.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -320,7 +320,7 @@ the page issues the protected request.
320
320
  Always report the evidence with file and line references:
321
321
 
322
322
  ```text
323
- Backend: theair-customer-backend/build.gradle.kts
323
+ Backend: customer-backend/build.gradle.kts
324
324
  Java 21 - java.toolchain.languageVersion (line 14)
325
325
  Spring Boot 3.2.1 - org.springframework.boot plugin (line 3)
326
326
  Spring MVC - spring-boot-starter-web (line 20)