@credenceanalytics/credmktcli
Advanced tools
Support for market place page where in any kind of feature like report/app/noderedflow can be published. User can visit market place download the Package and install.
$ npm install -g @credenceanalytics/credmktcli@latest
$ credmktcli --help
credmkt-cli folder to somewhere safe on your disk.npm link --force inside credmkt-cli/ folder.$ credmktcli --help
Run this command in the credence/ folder.
This command creates a new directory named custom-packages/ in the credence/ Folder.
$ credmktcli setup
credence/
├── visualizer-dashpages/
├── pages/
├── apps/
└── microservices/
credence/
├── custom-packages/
├── visualizer-dashpages/
├── apps/
├── pages/
└── microservices/
Run this command in package repository must be a git repo.
This command helps in setting up a new package by creating a package.json file in the specified directory. It prompts the user to enter various details about the package such as name, version, description, author and keywords and writes these details into a newly created package.json file.
$ credmktcli package:init
<Package repo>/
└── package.json
This command is used to add a new visualizer dashboard or pagebuilder page to an existing package in a Git repository.
This command checks if the current directory is a Git repository and contains a package.json file. It then prompts the user to choose whether to add a visualizer dashboard or pagebuilder page to the package. If a visualizer dashboard already exists in the package, the user is asked whether they want to overwrite it.
This command is not for reports
$ credmktcli package:add
<Package repo>/
└── package.json
└── <Package repo>/
├── visualizer-dashboard/
│ └── <Added dashboard>/
│ └── files
├── pages/
│ └── <Added pages/
│ └── files
└── package.json
This command is used to update the version of a package, commit and push changes to the Git repository, and create a ZIP archive of the package.
$ credmktcli package:publish
└── <Package repo>/
├── visualizer-dashboard/
│ └── <Added dashboard>/
│ └── files
├── pages/
│ └── <Added pages/
│ └── files
└── package.json
This command is used to extract and install a package from a specified ZIP file. This command handles extracting the package, optionally overwriting existing directories, and setting up the package correctly.
$ credmktcli package:apply
└── credence/
├── custom-packages/
├── visualizer-dashpages/
├── apps/
├── microservices/
└── pages/
credence/
├── custom-packages/
│ └── <Installed Package>/
│ ├── visualizer-dashboard/
│ │ └── <different dashboards>
| ├──pages/
| | └──<different pages>
│ └── package.json
├── visualizer-dashpages/
│ └── dash/
│ └── <different dashboards>
├── pages/
| └──<different pages>
├── apps
└── microservices
This command applies multiple packages in version order from the updates/packages/ folder. It discovers all package ZIP files in the updates/packages/ subfolder, sorts them by semantic version, and applies them sequentially with comprehensive error handling and recovery.
Run this command in the credence/ folder.
$ credmktcli package:update
credence/
└── updates/
└── packages/
├── mypackage-1.0.0.zip
├── mypackage-1.1.0.zip
├── anotherpackage-2.0.0.zip
└── anotherpackage-2.1.0.zip
All package ZIP files must follow the naming pattern: <package-name>-<version>.zip
Examples of valid names:
dashboard-reports-1.0.0.zipuser-analytics-2.1.3.zipcustom-widgets-1.5.0.zipupdates/packages/ folder for ZIP files.failed files with error details└── credence/
├── custom-packages/
├── updates/
│ └── packages/
│ ├── package-a-1.0.0.zip
│ ├── package-a-1.1.0.zip
│ └── package-b-2.0.0.zip
├── visualizer-dashpages/
├── apps/
├── microservices/
└── pages/
credence/
├── custom-packages/
│ ├── package-a-1.1.0/
│ │ ├── visualizer-dashboard/
│ │ │ └── <dashboards>
│ │ ├── pages/
│ │ │ └── <pages>
│ │ └── cred_package.json
│ └── package-b-2.0.0/
│ ├── reports/
│ │ └── <reports>
│ └── cred_package.json
├── updates/
│ └── packages/
│ ├── package-a-1.0.0.zip
│ ├── package-a-1.1.0.zip
│ ├── package-b-2.0.0.zip
│ └── package-a-1.0.0.failed (if failed)
├── visualizer-dashpages/
│ └── dash/
│ └── <applied dashboards>
├── pages/
│ └── <applied pages>
├── apps
└── microservices
Run credmktcli setup (one time only) command
Run credmktcli package:init command
First export your report using Export button from Report Manager view.
Extract zip and copy/paste .rptdesign and .json file in you package git repository inside reports/ folder.
Package git repository structure:
.
└── <Package git repository>/
├── .git/
├── reports/
│ ├── <some report>.rptdesign
│ └── <some report>.json
└── package.json
Run credmktcli package:publish command to push changes. It will also create -.zip file
Use this zip in credmktcli package:apply command
FAQs
Credence Marketplace CLI Tool
We found that @credenceanalytics/credmktcli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 12 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket is launching experimental protection for the Hugging Face ecosystem, scanning for malware and malicious payload injections inside model files to prevent silent AI supply chain attacks.
Research
/Security News
The Socket Threat Research Team uncovered a coordinated campaign that floods the Chrome Web Store with 131 rebranded clones of a WhatsApp Web automation extension to spam Brazilian users.
Security News
ENISA’s 2025 Threat Landscape report highlights how AI is reshaping cyber attacks, driving phishing, model poisoning, and software supply chain risks.