@hashmark/cli
Advanced tools
sudo npm install -g @hashmark/cli
Once installed, the CLI is available through the hm command. Currently, the only available command is hm convert, which parses a hashmark document:
$ hm convert --help
hm convert [options] <file>
Convert Hashmark files
Positionals:
file Path to a Hashmark file [string] [required]
Options:
--version, -v Show version number [boolean]
--help, -h Show help [boolean]
--format, -f
[string] [choices: "auto", "json", "xml"] [default: "auto": infers the format
from the output file. Defaults to "json"]
--output, -o Write output to a file [string]
Clone the repository, and install dependencies with:
npm install
To build the project, run:
npm run build
To run the build, you can link the built files to your PATH by running:
sudo npm link
This will make the built files available under the hm command. You can run npm run build to re-build, and hm will now run your latest build. To unlink the hm command from the built file, run:
sudo npm unlink
FAQs
CLI for Hashmark documents
We found that @hashmark/cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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.
Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.
Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.