
Research
/Security News
Popular Tinycolor npm Package Compromised in Supply Chain Attack Affecting 40+ Packages
Malicious update to @ctrl/tinycolor on npm is part of a supply-chain attack hitting 40+ packages across maintainers
@penrose/automator
Advanced tools
This package is a command-line application that depends on `@penrose/core` and batch-processes multiple Penrose diagrams.
@penrose/automator
: a headless renderer for PenroseThis package is a command-line application that depends on @penrose/core
and batch-processes multiple Penrose diagrams.
Usage:
Penrose Automator.
Usage:
automator batch LIB OUTFOLDER [--folders] [--src-prefix=PREFIX] [--repeat=TIMES] [--render=OUTFOLDER]
automator render ARTIFACTSFOLDER OUTFOLDER
Options:
-o, --outFile PATH Path to either an SVG file or a folder, depending on the value of --folders. [default: output.svg]
--folders Include metadata about each output diagram. If enabled, outFile has to be a path to a folder.
--src-prefix PREFIX the prefix to SUBSTANCE, STYLE, and DOMAIN, or the library equivalent in batch mode. No trailing "/" required. [default: .]
--repeat TIMES the number of instances
yarn start batch registry.json out/ --src-prefix=../../examples
in this directory. The output SVGs will appear in out
.automator
for local developmentcore
(e.g. Synthesizer
), you can run yarn start
in the project root direcory, which will continuously watch your changes in core
and update your build.automator
to make sure your changes in core
are not causing any errors.automator
will now be using the most recent version of core
when batch-processing Penrose programs.In addition to batch-processing Penrose programs, you can also use automator
to generate a static site for viewing the diagrams and metadata (e.g. performance statistics). Here's an example:
yarn start batch registry.json out/ --src-prefix=../../examples --folders
in this directory.
--folders
option asks automator
to output metadata along with SVGs. automator render
requires the output to have associated metadata.yarn start render out browser
to generate a static site.browser/index.html
to view the result.FAQs
This package is a command-line application that depends on `@penrose/core` and batch-processes multiple Penrose diagrams.
The npm package @penrose/automator receives a total of 0 weekly downloads. As such, @penrose/automator popularity was classified as not popular.
We found that @penrose/automator demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 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
/Security News
Malicious update to @ctrl/tinycolor on npm is part of a supply-chain attack hitting 40+ packages across maintainers
Security News
pnpm's new minimumReleaseAge setting delays package updates to prevent supply chain attacks, with other tools like Taze and NCU following suit.
Security News
The Rust Security Response WG is warning of phishing emails from rustfoundation.dev targeting crates.io users.