Generate a THIRDPARTY file with all licenses in a cargo project.

Overview

cargo-bundle-licenses

Build Status license Version info

Bundle all third-party licenses into a single file.

NOTE This tools is not a lawyer and no guarantee of correctness can be made regarding the licenses that it selects. This tool relies on the information supplied in package metadata to be correct, this is not guaranteed so for "real" scenarios it is recommended that all licenses be reviewed and verified manually as well.

Install

cargo install cargo-bundle-licenses

Usage

The typical use case for this tool is as follows:

  1. Generate an initial bundle file:
cargo bundle-licenses --format yaml --output THIRDPARTY.yml
  1. Go through the listed warnings and track down licenses that could not be found and paste the text of the license into the "THIRDPARTY.yml" file.
    • Note: if the licence should have been found by cargo-bundle-licenses then please create an issue, or even better, a pull request!
  2. In your CI, run cargo-bundle-licenses in the following way to check for changes and fail if they are found. This will generate a new thirdparty file, apply any licenses that have been added by hand to fill in the "NOT FOUND" licenses, and then compare the newly generated version against the previous version and fail if there are any differences.
cargo bundle-licenses --format yaml --output CI.yaml --previous THIRDPARTY.yml --check-previous

To aid in copy-pasting licenses that couldn't be found for one reason other another the esc tool can be used to properly create escaped license strings to drop into the format of your choosing.

Formats

Currently the supported formats are json, yaml, and toml. A more human readable format that is closer to a classical THIRDPARTY file and already has serde support is being actively sought. Please create an issue or PR if you have an idea for this.

Common warnings and resolutions

The most common cause of missing licenses seems to be workspaces that don't include forward their license files. Go to the repo for the workspace and copy the relevant files from there.

A package license may receive a confidence warning stating that cargo-bundle-licenses is "unsure" or "semi" confident. This means that when the found license was compared to a template license it was found to have diverged in more than a few words. You should verify that the licence text is in fact correct in these cases.

Differences from other tools

  • cargo-about also finds and aggregates the license texts of all dependencies. cargo-bundle-licenses is different in that it is focused more on generating something and then allowing that to be manually updated with not-found licenses whereas cargo-about will not generate output in that scenario. Additionally, cargo-bundle-licenses allows for manual updates to be applied to later versions of the thirdparty file. However, cargo-about does generate a very nice human readable format, and provides more granularity in what packages / licenses are allowed.
  • cargo-license only generates a list of licenses as found in the Cargo.toml files.
  • cargo-deny TODO

Attributions

This crate was heavily inspired by cargo-lichking.

Comments
  • parse license expressions using the spdx crate

    parse license expressions using the spdx crate

    This is an attempt to fix issue sstadick/cargo-bundle-licenses#10

    This uses the spdx crate to parse the license expression and extracts the licenses from that parsed expression. Crates.io uses the spdx crate to validate that the license expression is valid: https://github.com/rust-lang/crates.io/blob/87bce69097c486f704e0848245726c14a8a04441/src/models/version.rs#L191-L204

    In case spdx can't parse the license expression it false back to the old license handling. This also includes some tests to check that existing mappings are still mapped correctly.

    opened by Skgland 4
  • Removing/ignoring CARGO_HOME prefix?

    Removing/ignoring CARGO_HOME prefix?

    I'm using cargo-bundle-license in my CI to alert me when licenses have changed. However, the license file checker is sensitive to the $CARGO_HOME variable, so if I commit the license bundle on one system (my local machine) and check for compliance on another (the CI machines), then I'm likely to get nonsense messages, like this:

    [2022-03-16T13:17:41Z ERROR bundle_licenses_lib::bundle] Previous ring:0.16.20 does not match new ring:0.16.20

    All that's different is license file path e.g.

    -    license: License specified in file (/usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/LICENSE)
    +    license: License specified in file (/go/src/github.com/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/LICENSE)
    

    As far as I can tell, this isn't a useful thing. Maybe something like $CARGO_HOME/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/LICENSE can be stored instead, with the variable not expanded?

    good first issue 
    opened by morrisonlevi 4
  • Complex SPDX Expressions

    Complex SPDX Expressions

    I noticed that for the encoding_rs dependency resulting licenses are weired.

    Running the following script:

    #!/bin/bash
    
    cargo init example
    pushd example
     
    echo -e "encoding_rs = '0.8.31'\n" >> Cargo.toml 
    cargo bundle-licenses --format toml --output THIRDPARTY.toml
    cat THIRDPARTY.toml
    popd
    

    I get the following output:

    Created binary (application) package
    ~/Git/tmp/bundle/example ~/Git/tmp/bundle
    [2022-04-30T19:14:37Z WARN  bundle_licenses_lib::found_license] No license found for (Apache-2.0 license in encoding_rs:0.8.31 - /home/bennet/.cargo/registry/src/github.com-1ecc6299db9ec823/encoding_rs-0.8.31/Cargo.toml
    [2022-04-30T19:14:37Z WARN  bundle_licenses_lib::found_license] No license found for MIT) AND BSD-3-Clause license in encoding_rs:0.8.31 - /home/bennet/.cargo/registry/src/github.com-1ecc6299db9ec823/encoding_rs-0.8.31/Cargo.toml
    root_name = "example"
    
    [[third_party_libraries]]
    package_name = "cfg-if"
    package_version = "1.0.0"
    license = "MIT / Apache-2.0"
    
    [[third_party_libraries.licenses]]
    license = "MIT"
    text = "Copyright (c) 2014 Alex Crichton\n\nPermission is hereby granted, free of charge, to any\nperson obtaining a copy of this software and associated\ndocumentation files (the \"Software\"), to deal in the\nSoftware without restriction, including without\nlimitation the rights to use, copy, modify, merge,\npublish, distribute, sublicense, and/or sell copies of\nthe Software, and to permit persons to whom the Software\nis furnished to do so, subject to the following\nconditions:\n\nThe above copyright notice and this permission notice\nshall be included in all copies or substantial portions\nof the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF\nANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED\nTO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A\nPARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT\nSHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY\nCLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION\nOF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR\nIN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER\nDEALINGS IN THE SOFTWARE.\n"
    
    [[third_party_libraries.licenses]]
    license = "Apache-2.0"
    text = "                              Apache License\n                        Version 2.0, January 2004\n                     http://www.apache.org/licenses/\n\nTERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n\n1. Definitions.\n\n   \"License\" shall mean the terms and conditions for use, reproduction,\n   and distribution as defined by Sections 1 through 9 of this document.\n\n   \"Licensor\" shall mean the copyright owner or entity authorized by\n   the copyright owner that is granting the License.\n\n   \"Legal Entity\" shall mean the union of the acting entity and all\n   other entities that control, are controlled by, or are under common\n   control with that entity. For the purposes of this definition,\n   \"control\" means (i) the power, direct or indirect, to cause the\n   direction or management of such entity, whether by contract or\n   otherwise, or (ii) ownership of fifty percent (50%) or more of the\n   outstanding shares, or (iii) beneficial ownership of such entity.\n\n   \"You\" (or \"Your\") shall mean an individual or Legal Entity\n   exercising permissions granted by this License.\n\n   \"Source\" form shall mean the preferred form for making modifications,\n   including but not limited to software source code, documentation\n   source, and configuration files.\n\n   \"Object\" form shall mean any form resulting from mechanical\n   transformation or translation of a Source form, including but\n   not limited to compiled object code, generated documentation,\n   and conversions to other media types.\n\n   \"Work\" shall mean the work of authorship, whether in Source or\n   Object form, made available under the License, as indicated by a\n   copyright notice that is included in or attached to the work\n   (an example is provided in the Appendix below).\n\n   \"Derivative Works\" shall mean any work, whether in Source or Object\n   form, that is based on (or derived from) the Work and for which the\n   editorial revisions, annotations, elaborations, or other modifications\n   represent, as a whole, an original work of authorship. For the purposes\n   of this License, Derivative Works shall not include works that remain\n   separable from, or merely link (or bind by name) to the interfaces of,\n   the Work and Derivative Works thereof.\n\n   \"Contribution\" shall mean any work of authorship, including\n   the original version of the Work and any modifications or additions\n   to that Work or Derivative Works thereof, that is intentionally\n   submitted to Licensor for inclusion in the Work by the copyright owner\n   or by an individual or Legal Entity authorized to submit on behalf of\n   the copyright owner. For the purposes of this definition, \"submitted\"\n   means any form of electronic, verbal, or written communication sent\n   to the Licensor or its representatives, including but not limited to\n   communication on electronic mailing lists, source code control systems,\n   and issue tracking systems that are managed by, or on behalf of, the\n   Licensor for the purpose of discussing and improving the Work, but\n   excluding communication that is conspicuously marked or otherwise\n   designated in writing by the copyright owner as \"Not a Contribution.\"\n\n   \"Contributor\" shall mean Licensor and any individual or Legal Entity\n   on behalf of whom a Contribution has been received by Licensor and\n   subsequently incorporated within the Work.\n\n2. Grant of Copyright License. Subject to the terms and conditions of\n   this License, each Contributor hereby grants to You a perpetual,\n   worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n   copyright license to reproduce, prepare Derivative Works of,\n   publicly display, publicly perform, sublicense, and distribute the\n   Work and such Derivative Works in Source or Object form.\n\n3. Grant of Patent License. Subject to the terms and conditions of\n   this License, each Contributor hereby grants to You a perpetual,\n   worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n   (except as stated in this section) patent license to make, have made,\n   use, offer to sell, sell, import, and otherwise transfer the Work,\n   where such license applies only to those patent claims licensable\n   by such Contributor that are necessarily infringed by their\n   Contribution(s) alone or by combination of their Contribution(s)\n   with the Work to which such Contribution(s) was submitted. If You\n   institute patent litigation against any entity (including a\n   cross-claim or counterclaim in a lawsuit) alleging that the Work\n   or a Contribution incorporated within the Work constitutes direct\n   or contributory patent infringement, then any patent licenses\n   granted to You under this License for that Work shall terminate\n   as of the date such litigation is filed.\n\n4. Redistribution. You may reproduce and distribute copies of the\n   Work or Derivative Works thereof in any medium, with or without\n   modifications, and in Source or Object form, provided that You\n   meet the following conditions:\n\n   (a) You must give any other recipients of the Work or\n       Derivative Works a copy of this License; and\n\n   (b) You must cause any modified files to carry prominent notices\n       stating that You changed the files; and\n\n   (c) You must retain, in the Source form of any Derivative Works\n       that You distribute, all copyright, patent, trademark, and\n       attribution notices from the Source form of the Work,\n       excluding those notices that do not pertain to any part of\n       the Derivative Works; and\n\n   (d) If the Work includes a \"NOTICE\" text file as part of its\n       distribution, then any Derivative Works that You distribute must\n       include a readable copy of the attribution notices contained\n       within such NOTICE file, excluding those notices that do not\n       pertain to any part of the Derivative Works, in at least one\n       of the following places: within a NOTICE text file distributed\n       as part of the Derivative Works; within the Source form or\n       documentation, if provided along with the Derivative Works; or,\n       within a display generated by the Derivative Works, if and\n       wherever such third-party notices normally appear. The contents\n       of the NOTICE file are for informational purposes only and\n       do not modify the License. You may add Your own attribution\n       notices within Derivative Works that You distribute, alongside\n       or as an addendum to the NOTICE text from the Work, provided\n       that such additional attribution notices cannot be construed\n       as modifying the License.\n\n   You may add Your own copyright statement to Your modifications and\n   may provide additional or different license terms and conditions\n   for use, reproduction, or distribution of Your modifications, or\n   for any such Derivative Works as a whole, provided Your use,\n   reproduction, and distribution of the Work otherwise complies with\n   the conditions stated in this License.\n\n5. Submission of Contributions. Unless You explicitly state otherwise,\n   any Contribution intentionally submitted for inclusion in the Work\n   by You to the Licensor shall be under the terms and conditions of\n   this License, without any additional terms or conditions.\n   Notwithstanding the above, nothing herein shall supersede or modify\n   the terms of any separate license agreement you may have executed\n   with Licensor regarding such Contributions.\n\n6. Trademarks. This License does not grant permission to use the trade\n   names, trademarks, service marks, or product names of the Licensor,\n   except as required for reasonable and customary use in describing the\n   origin of the Work and reproducing the content of the NOTICE file.\n\n7. Disclaimer of Warranty. Unless required by applicable law or\n   agreed to in writing, Licensor provides the Work (and each\n   Contributor provides its Contributions) on an \"AS IS\" BASIS,\n   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n   implied, including, without limitation, any warranties or conditions\n   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n   PARTICULAR PURPOSE. You are solely responsible for determining the\n   appropriateness of using or redistributing the Work and assume any\n   risks associated with Your exercise of permissions under this License.\n\n8. Limitation of Liability. In no event and under no legal theory,\n   whether in tort (including negligence), contract, or otherwise,\n   unless required by applicable law (such as deliberate and grossly\n   negligent acts) or agreed to in writing, shall any Contributor be\n   liable to You for damages, including any direct, indirect, special,\n   incidental, or consequential damages of any character arising as a\n   result of this License or out of the use or inability to use the\n   Work (including but not limited to damages for loss of goodwill,\n   work stoppage, computer failure or malfunction, or any and all\n   other commercial damages or losses), even if such Contributor\n   has been advised of the possibility of such damages.\n\n9. Accepting Warranty or Additional Liability. While redistributing\n   the Work or Derivative Works thereof, You may choose to offer,\n   and charge a fee for, acceptance of support, warranty, indemnity,\n   or other liability obligations and/or rights consistent with this\n   License. However, in accepting such obligations, You may act only\n   on Your own behalf and on Your sole responsibility, not on behalf\n   of any other Contributor, and only if You agree to indemnify,\n   defend, and hold each Contributor harmless for any liability\n   incurred by, or claims asserted against, such Contributor by reason\n   of your accepting any such warranty or additional liability.\n\nEND OF TERMS AND CONDITIONS\n\nAPPENDIX: How to apply the Apache License to your work.\n\n   To apply the Apache License to your work, attach the following\n   boilerplate notice, with the fields enclosed by brackets \"[]\"\n   replaced with your own identifying information. (Don't include\n   the brackets!)  The text should be enclosed in the appropriate\n   comment syntax for the file format. We also recommend that a\n   file or class name and description of purpose be included on the\n   same \"printed page\" as the copyright notice for easier\n   identification within third-party archives.\n\nCopyright [yyyy] [name of copyright owner]\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n\thttp://www.apache.org/licenses/LICENSE-2.0\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n"
    
    [[third_party_libraries]]
    package_name = "encoding_rs"
    package_version = "0.8.31"
    license = "(Apache-2.0 / MIT) AND BSD-3-Clause"
    
    [[third_party_libraries.licenses]]
    license = "(Apache-2.0"
    text = "NOT FOUND"
    
    [[third_party_libraries.licenses]]
    license = "MIT) AND BSD-3-Clause"
    text = "NOT FOUND"
    ~/Git/tmp/bundle
    

    the weird part about this is the two licenses (Apache-2.0, and MIT) AND BSD-3-Clause. Instead I would have expected three licenses Apache-2.0, MIT, and BSD-3-Clause.

    Additionally, it appears OR is normalised to / which I find peculiar as a footnote in the Cargo Manifest Documentation states that Previously multiple licenses could be separated with a /, but that usage is deprecated, so I would have rather expected a normalisation to OR or no normalisation at all.

    opened by Skgland 2
  • Make it possible to disable dependencies only used by the binary

    Make it possible to disable dependencies only used by the binary

    Adds a feature required by the binary to enable the dependencies only used by it. The feature is set as a default feature so it does not need to be specified explicitly when building the binary. When using the lib one would probably want to disable default features to remove the unnecessary dependencies.

    An alternative would be to spilt the project into two packages one with the library and one with the binary to specify the dependencies independently, though that would require more churn.

    opened by Skgland 1
  • Add BSD-2-Clause

    Add BSD-2-Clause

    As discussed in #4

    By the way, how about just parsing SPDX with the license name? Everything's in GitHub: https://github.com/spdx/license-list-XML/tree/master/src (Just for the future)

    opened by BastianZim 0
  • License files not found for aspect-rs

    License files not found for aspect-rs

    Hello, I was testing out this tool, and I noticed that the license files were not found for the aspect or aspect-weave crates. The problem is that both crates are in the same repository, as subdirectories. The LICENSE files are located at the top level. I'm not sure if there's an easy way to resolve this issue, but I figured I would file it.

    opened by pcd1193182 1
  • Add clean Apache-2.0

    Add clean Apache-2.0

    I'm not yet sure how to do this but it would be great if the two Apache-2.0 formats could be supported.

    Currently, the included license contains the APPENDIX: How to apply the Apache License to your work which is not always included in the actual license: https://www.apache.org/licenses/LICENSE-2.0

    This leads to semi confidence results for packages. Example retworkx-core: https://github.com/Qiskit/retworkx/blob/main/retworkx-core/LICENSE

    opened by BastianZim 1
  • No template found for BSD-2-Clause

    No template found for BSD-2-Clause

    Hi,

    my knowledge of rust is exactly zero so sorry if this is something obvious. One of the packages I'm running this on (retworkx) has a dependency on numpy where I'm getting the following error:

    [2021-12-11T17:23:33Z WARN  bundle_licenses_lib::found_license] No template for BSD-2-Clause license in numpy:0.15.0 - /Users/bastianzimmermann/.cargo/registry/src/github.com-1ecc6299db9ec823/numpy-0.15.0/Cargo.toml
    

    I would assume that this is from the template check mentioned in the readme. I can find BSD-2-Clause in here but no idea if this is the right place to look and if something should be changed here: https://github.com/sstadick/cargo-bundle-licenses/blob/f824e2f97ba9372b87ae116f7f5f1591c20fba74/src/license.rs

    opened by BastianZim 10
  • `license-file` key in Cargo manifest is not read for path dependencies in a workspace

    `license-file` key in Cargo manifest is not read for path dependencies in a workspace

    Running

    cargo bundle-licenses -f yaml -o thirdparty.yaml
    

    as of https://github.com/artichoke/artichoke/pull/1420

    does not resolve the license text for path dependencies in this cargo workspace:

    # snip
      - package_name: artichoke-backend
        package_version: 0.2.0
        license: MIT
        licenses:
          - license: MIT
            text: NOT FOUND
      - package_name: artichoke-core
        package_version: 0.9.0
        license: MIT
        licenses:
          - license: MIT
            text: NOT FOUND
      - package_name: artichoke-load-path
        package_version: 0.1.0
        license: MIT
        licenses:
          - license: MIT
            text: NOT FOUND
    # snip
    

    See also: https://github.com/EmbarkStudios/cargo-about/issues/162

    opened by lopopolo 2
Releases(v1.0.1)
Owner
Seth
Principal Bioinformatics Engineer @fulcrumgenomics
Seth
A cli utility written in Rust that allows fetching all the labels of a project, save those as a YAML file

A cli utility written in Rust that allows fetching all the labels of a project, save those as a YAML file that you can easily edit or save as backup and apply a saved preset to new repositories.

Chevdor 4 May 5, 2022
cargo-lambda a Cargo subcommand to help you work with AWS Lambda

cargo-lambda cargo-lambda is a Cargo subcommand to help you work with AWS Lambda. This subcommand compiles AWS Lambda functions natively and produces

David Calavera 184 Jan 5, 2023
cargo-lambda is a Cargo subcommand to help you work with AWS Lambda.

cargo-lambda cargo-lambda is a Cargo subcommand to help you work with AWS Lambda. The new subcommand creates a basic Rust package from a well defined

null 184 Jan 5, 2023
A cargo subcommand that extends cargo's capabilities when it comes to code generation.

cargo-px Cargo Power eXtensions Check out the announcement post to learn more about cargo-px and the problems it solves with respect to code generatio

Luca Palmieri 33 May 7, 2023
A simple to use rust package to generate or parse Twitter snowflake IDs,generate time sortable 64 bits unique ids for distributed systems

A simple to use rust package to generate or parse Twitter snowflake IDs,generate time sortable 64 bits unique ids for distributed systems (inspired from twitter snowflake)

houseme 5 Oct 6, 2022
Bongo Copy Cat wants to be involved in everything you do but instead just imitates you hitting your keyboard all day. After all it's just a cat.

Bongo Copy Cat Introduction Bongo Copy Cat wants to be involved in everything you do but instead just imitates you hitting your keyboard all day. Afte

Abhijeet Singh 4 Jan 23, 2023
cargo, make me a project

cargo-generate cargo, make me a project cargo-generate is a developer tool to help you get up and running quickly with a new Rust project by leveragin

null 1.2k Jan 3, 2023
A tool that generates a Sublime Text project file that helps you get started using Scoggle.

README A tool that generates a Sublime Text project file that helps you get started using Scoggle. While Scoggle-Gen may not find every single source

Sanjiv Sahayam 0 Jan 10, 2022
Render cargo dependency tree in online

Cargo Tree Online Check out rendered page Render cargo dependency tree in online. Usage trunk serve Copy and paste the content of Cargo.lock file to

Kangwook Lee (이강욱) 2 Sep 23, 2021
Rust+Cargo lightweight hello world with the most minimum binary size possible.

Lightweight Cargo Hello World Rust+Cargo lightweight hello world with the most minimum binary size possible. requirements 1: Rustup (Rustc, Cargo) Ins

Raymond 1 Dec 13, 2021
Plugin to request a relaunch when uploading a Skyline plugin through cargo skyline

restart-plugin A skyline plugin for allowing cargo-skyline (or other tools) to restart your game without you having to touch your controller. Install

null 1 Nov 21, 2021
Convenience wrapper for cargo buildscript input/output

A convenience wrapper for cargo buildscript input/output. Why? The cargo buildscript API is (necessarily) stringly-typed.

Christopher Durham 6 Sep 25, 2022
A cargo subcommand that displays the assembly generated for Rust source code

cargo-show-asm A cargo subcommand that displays the assembly generated for Rust source code.

null 193 Dec 29, 2022
Cargo subcommand for optimizing binaries with PGO and BOLT.

cargo-pgo Cargo subcommand that makes it easier to use PGO and BOLT to optimize Rust binaries. Installation $ cargo install cargo-pgo You will also ne

Jakub Beránek 229 Dec 28, 2022
Mommy's here to support you when running cargo~

cargo-mommy Mommy's here to support you when running cargo~ ❤️ Installation Install cargo-mommy like you would any other cargo extension~ > cargo inst

Aria Beingessner 198 Jan 5, 2023
Load and resolve Cargo configuration.

cargo-config2 Load and resolve Cargo configuration. This library is intended to accurately emulate the actual behavior of Cargo configuration, for exa

Taiki Endo 6 Jan 10, 2023
Cargo-BOJ: test and submit solutions to BOJ problems

Cargo-BOJ Test and submit solutions to BOJ (Baekjoon Online Judge) problems. Defaults are geared towards Rust solutions, but non-Rust usage is support

null 5 Apr 3, 2023
Cargo wrapper for working with Webassembly wasi(x).

cargo-wasix A cargo subcommand that wraps regular cargo commands for compiling Rust code to wasix, a superset of Websassembly wasi with additional fun

WASIX 19 Jun 12, 2023
Cargo subcommand to easily bootstrap nocode applications. Write nothing; deploy nowhere.

cargo-nocode No code is the best way to write secure and reliable applications. Write nothing; deploy nowhere. cargo-nocode aims to bring the nocode a

Orhun Parmaksız 29 Jul 1, 2023