@brightsec/cli 13.7.0-next.3 → 13.7.0-next.5

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.
Files changed (4) hide show
  1. package/README.md +5 -5
  2. package/dist/index.js +1 -1
  3. package/dist/index.js.map +1 -1
  4. package/package.json +1 -1
package/README.md CHANGED
@@ -7,10 +7,10 @@ The NPM allows you to install the Bright Command Line Interface (CLI) on your ma
7
7
  ##### Features:
8
8
 
9
9
  - Easy control of the Bright REST API.
10
- - [Repeater mode](https://docs.brightsec.com/docs/initializing-the-repeater), which allows the Bright cloud engine to connect to local targets securely, pulling all scan requests as outbound traffic, without exposing the targets to the Internet.
10
+ - [Repeater mode](https://docs.brightsec.com/docs/on-premises-repeater-local-agent), which allows the Bright cloud engine to connect to local targets securely, pulling all scan requests as outbound traffic, without exposing the targets to the Internet.
11
11
  - Flexible proxy configuration, which allows you to control the CLI requests both internally and externally.
12
12
  - Connector to on-premises (local) ticketing services. For example, you can enable the Bright integration with on-premises Jira, for tickets to be automatically opened for each security vulnerability detected.
13
- - Integration of Bright with your CI pipelines. Please see our [guide on integrating Bright with CI pipelines](https://docs.brightsec.com/docs/integrate-bright-with-your-ci-pipeline) for more information.
13
+ - Integration of Bright with your CI pipelines. Please see our [guide on integrating Bright with CI pipelines](https://docs.brightsec.com/docs/integrate-bright-with-your-cicd-pipeline) for more information.
14
14
  - Running commands from a configuration file. You can run the CLI commands from your console or save them as a JSON, XML, YML, or JavaScript file. Running the CLI from a pre-configured file will simplify further scanning.
15
15
 
16
16
  ## 🔎 Table of Contents
@@ -69,14 +69,14 @@ We recommend that you use the `--smart` option to optimize the scan coverage and
69
69
 
70
70
  #### 4. Check out the scan results
71
71
 
72
- You can follow the scan status in the [Bright app](https://app.brightsec.com/scans) or by using the [**Bright CLI** polling](https://docs.brightsec.com/docs/checking-scan-status) command.
72
+ You can follow the scan status in the [Bright app](https://app.brightsec.com/scans) or by using the [**Bright CLI** polling](https://docs.brightsec.com/docs/cli-checking-scan-status) command.
73
73
 
74
74
  ## 📚 Full Documentation
75
75
 
76
- The **Bright CLI** can do so much more! You can find a full guide with the usage examples in the [Bright docs](https://docs.brightsec.com/docs/getting-started-with-bright-cli).
76
+ The **Bright CLI** can do so much more! You can find a full guide with the usage examples in the [Bright docs](https://docs.brightsec.com/docs/about-bright-cli).
77
77
 
78
78
  ## 📝 License
79
79
 
80
- Copyright © 2024 [Bright Security Inc.](https://brightsec.com/)
80
+ Copyright © 2025 [Bright Security Inc.](https://brightsec.com/)
81
81
 
82
82
  This project is licensed under the MIT License - see the [LICENSE file](LICENSE) for details.