purl-spec
mason-registry
purl-spec | mason-registry | |
---|---|---|
4 | 5 | |
621 | 125 | |
2.9% | 8.8% | |
4.8 | 10.0 | |
22 days ago | 3 days ago | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
purl-spec
- Purl: A Simple Tool for Text Processing
- Package URL Specification
-
PSA: Changes to the mason.nvim registry
Makes heavy use of purls to define package sources. This aids portability of package identifiers, which is currently leveraged to automate version upgrades through Renovate and hopefully can be used to hook into vulnerability databases such as NVD for automated security scanning purposes.
-
OSS Gadget: Using oss-download
The oss-download tool operates on a Package URL, which is a convenient way to express an ecosystem, package, and version. For example, the Python Django package would be pkg:pypi/django, and version 4.1.4 of Django would be pkg:pypi/[email protected].
mason-registry
-
Show HN: Postgres Language Server
Can you try to get it added to Mason so people don't have to try and do a custom install?
https://github.com/mason-org/mason-registry/
- saltstack development in neovim
-
Astronvim Python DAP not starting
There was a bug in the new mason registry that I fixed this morning: https://github.com/mason-org/mason-registry/pull/1056
-
PSA: Changes to the mason.nvim registry
Hello! This is a PSA for people who use mason.nvim (tl;dr at the bottom). Going forward the core registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This decouples the infrastructure in such a way that the Lua plugin becomes a standalone client that can be hooked into more registries than just the core one, as well as more easily be subject to versioning (mason.nvim currently doesn't version itself due to the fact that packages are bundled with it, which complicates things). This decoupling also lowers the barrier of entry for additional maintainers who can solely focus on the registry, without having to learn the internals of the plugin (more info will come soon if you're interested in possibly helping maintain the core registry).
Going forward the core mason.nvim package registry will be hosted as a collection of static, YAML-based, package definitions at https://github.com/mason-org/mason-registry, as opposed to bundled with the mason.nvim plugin itself as Lua modules. This will be a fully seamless migration so you shouldn't notice anything and there is no action required. Refer to the full announcement post for more information.
What are some alternatives?
OSSGadget - Collection of tools for analyzing open source packages.
atlas - Manage your database schema as code
rebom - Rebom by Reliza - Catalog of Software Bills of Materials (SBOMs), demo:
declarative-schemas
dependency-track - Dependency-Track is an intelligent Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain.
nil - NIx Language server, an incremental analysis assistant for writing in Nix.
language-server-protocol - Defines a common protocol for language servers.
vscode-postgres - PostgreSQL extension for vscode providing explorer, highlighting, diagnostics, and intellisense
renovate - Universal dependency automation tool.
json-schema-spec - The JSON Schema specification
astrocommunity - A community repository of common plugin specifications
postgres-ast-deparser - A PostgreSQL AST toolkit and deparser, written in pure plpgsql