Search Results for "claw-code"

Yarn is a package manager for your code. It allows you to use and share code with other developers from around the world. Yarn does this quickly, securely, and reliably so you don’t ever have to worry. Yarn allows you to use other developers’ solutions to different problems, making it easier for you to develop your software. If you have problems, you can report issues or contribute back, and when the problem is fixed, you can use Yarn to keep it all up to date.

FOSSA CLI is a command-line tool that scans your codebase to identify open-source dependencies and their associated licenses and vulnerabilities. It integrates into CI/CD pipelines to provide automated compliance checks, license audits, and security analysis. Designed for enterprise software teams, FOSSA CLI helps enforce open-source policies at scale and provides accurate, automated insights into third-party software usage through deep analysis of transitive dependencies and...

Maven is a project development management and comprehension tool. Based on the concept of a project object model: builds, dependency management, documentation creation, site publication, and distribution publication are all controlled from the pom.xml declarative file. Maven can be extended by plugins to utilize a number of other development tools for reporting or the build process.

...If you are building, testing, publishing, and deploying software on any platform, Gradle offers a flexible model that can support the entire development lifecycle from compiling and packaging code to publishing web sites. Gradle has been designed to support build automation across multiple languages and platforms including Java, Scala, Android, Kotlin, C/C++, and Groovy, and is closely integrated with development tools and continuous integration servers including Eclipse, IntelliJ, and Jenkins. From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster. ...

The Gradle Lint Plugin is a static analysis tool for Gradle build scripts (written in Groovy) that finds patterns of misuse, deprecated constructs, and opportunities for optimization in build configurations. It functions analogous to ESLint in the JavaScript ecosystem: you define rules, apply them across the build scripts, and get warnings or errors when code deviates from best practices. It is particularly useful for maintaining consistency across large, multi-module projects or monorepos, helping teams avoid build anti-patterns, unused dependencies, or misconfigurations. The plugin supports custom rules and can even automatically fix certain violations (e.g. unused dependencies) via a fixGradleLint task. ...

...The dependencies for your projects are specified in a single text file called a Podfile. CocoaPods will resolve dependencies between libraries, fetch the resulting source code, then link it together in an Xcode workspace to build your project. Ultimately the goal is to improve discoverability of, and engagement in, third party open-source libraries by creating a more centralised ecosystem.

box is an R package providing a modular system / module loader for organizing reusable R code outside of full packages. It allows users to treat R scripts (files/folders) as modules — possibly nested — with explicit exports, imports, and scoping. The idea is to let users structure code in a more modular, composable way, without needing every reusable component to be a full CRAN-style package. It also provides a cleaner syntax for importing functions or modules (via box::use) that allows scoping control and avoids global pollution. ...

ALI_Parse is a parser for the .ali files generated by the GNAT Ada compiler. ALI means Ada Library Information. You find the .ali files in the same directories as the object files (.o) containing the machine code produced by GNAT. Currently, ALI_Parse is focused at cross-references within a set of Ada source files. Two command-line tools using the parser are provided: * GNATHTML, which generates a set of Web pages from Ada sources * ALI_Stats, which shows the list of entities, the list of cross-references, the count of references to each entity and the list of files. ...

...It simplifies adding, updating, and removing package sources via a single nix/sources.json file, improving reproducibility and version control in Nix-based workflows. niv simplifies adding and updating dependencies in Nix projects. It uses a single file, nix/sources.json, where it stores the data necessary for fetching and updating the packages. Nix is a very powerful tool for building code and setting up environments. niv complements it by making it easy to describe and update remote dependencies (URLs, GitHub repos, etc). It is a simple, practical alternative to Nix flakes. The add command will infer information about the package being added, when possible. This works very well for GitHub repositories. Run this command to add jq to your project.