@codelaw/rules-js-fux-index
An optional Fux index of codelaw's js rules, at 0.2.0.
It is data only (the shards, identifiers.toml and fux-index.json), has no dependencies and is not
installed by codelaw init. codelaw itself never reads it; install it only if your repository uses Fux.
It indexes the files of @codelaw/rules-js at the same version, so install that pack too.
Pin it in .fux/config/plugins.toml with fux setup --index <PyPI name> --index-npm <npm name>:
- npm:
@codelaw/rules-js-fux-index - PyPI:
codelaw-rules-js-fux-index
Built with fux 5.1.1 from packs/js/rules/ of the codelaw repository (MIT).
1 maintainer
Metadata
1 maintainer
Release files for codelaw-rules-js-fux-index 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| codelaw_rules_js_fux_index-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for codelaw_rules_js_fux_index-0.2.0-py3-none-any.whl |
Release files / codelaw_rules_js_fux_index-0.2.0-py3-none-any.whl
| Download URL | codelaw_rules_js_fux_index-0.2.0-py3-none-any.whl |
|---|---|
| Size | 100.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
178cb30ae91faf8ce4662c77b077371df2b575f95970c001b31919b7545b9dbe
|
|
BLAKE2b-256 checksum How to use checksums |
021bc27b57148085e8cd57ccea424446b10e665ea6bc4287734288d254d05da0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for codelaw-rules-js-fux-index 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
