chronicle
syft
chronicle | syft | |
---|---|---|
2 | 32 | |
43 | 5,516 | |
- | 3.5% | |
8.5 | 9.8 | |
4 days ago | about 16 hours ago | |
Go | Go | |
Apache License 2.0 | 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.
chronicle
-
Git log is not a changelog
we use https://github.com/anchore/chronicle to generate release notes in a changelog format using the issues and PRs from GitHub as the source of truth. In this way time well spent in the curation of issues and PRs (which is something we need to do anyway) means that we automatically get release notes for free. (disclaimer: I'm the author of chronicle)
-
Keep a Changelog
The approach I like to take is to curate issues and PR with semantic titles and organize them by label ("bug", "enhancement", etc) or linking PRs to an already curated issue. This way automation can use these to generate the changlog for me on each release based on closed issues and unlinked PRs since the last release.
We wrote Chronicle to do that automation for us: https://github.com/anchore/chronicle .
The nice thing about this... since you typically curate issues during the development process anyway, if you're doing that right then you get a nice looking changlog for free! We use this approach with our core tools, Syft and Grype (some changlog examples: https://github.com/anchore/syft/releases/tag/v0.31.0 and https://github.com/anchore/grype/releases/tag/v0.26.1 ).
Always happy to hear new feature ideas and possible customizations for Chronicle (put in an issue and let's chat )!
syft
-
An Overview of Kubernetes Security Projects at KubeCon Europe 2023
Syft is a popular open source CLI tool created by Anchore for generating an SBOM from container images and filesystems. It’s designed to provide a catalog of dependencies for other tools to use as a data source. It supports many popular programming languages, package managers, and container image formats.
-
Launch HN: EdgeBit (YC W23) – live software vulnerability analysis
Inside of the SBOMs, we can detect a lot: https://github.com/anchore/syft#supported-ecosystems
You're right that the active/dormant detection needs to be customized per type of runtime. We cover rpm/deb, python and java with the node and others coming very soon. The compiled languages will be our main focus next. For example, Go binaries embed some dependency metadata in the binary itself.
Also related to this effort is the "in-toto" integrity chain: https://in-toto.io/in-toto/ Since we're already connecting build to run, we aim to complete the chain.
-
Building a software bill of materials (SBOM) using open source tools
Installing syft is pretty straight forward. On any Linux/Mac environment you can run the following command to install
- Free tool for generating SBOM and CVEs against source or binaries
-
'cargo auditable' can now be used as a drop-in replacement for Cargo
The data format is supported by cargo audit, Syft and Trivy. Reading it from your own tools is also very easy.
-
12 Things You Might Not Know About Buildpacks
A Software-Bill-of-Materials (SBOM) lists all the software components included in an image. Buildpacks support SBOMs in CycloneDX, Syft and SPDX formats.
-
`cargo audit` can now scan compiled binaries
I think you can already do that using Syft.
-
Keeping up with dependencies like a boss
I'll continue relying on Anitya for the feed and syft/grype to build my SBOM and track vulnerabilities.
-
Wake-up call: why it's urgent to deal with your hardcoded credentials
Today corporations, open source projects, nonprofit foundations, and even governments are all trying to figure out how to improve the global software supply chain security. While these efforts are more than welcome, for the moment, there is hardly any straightforward way for organizations to improve on that front.
-
3 ways to improve your OSS project's resilience for Hacktoberfest
Syft is a popular open source tool that generates SBOMs for software applications and also containers. You can execute it manually and include the generated artifacts into your release, but you can also automate the process using a GitHub Action that will be triggered whenever you have a new release on your repository.
What are some alternatives?
keep-a-changelog - If you build software, keep a changelog.
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
semantic-pull-requests
grype - A vulnerability scanner for container images and filesystems
chyle - Changelog generator : use a git repository and various data sources and publish the result on external services
cdxgen - Creates CycloneDX Bill of Materials (BOM) for your projects from source and container images. Supports many languages and package managers. Integrate in your CI/CD pipeline with automatic submission to Dependency Track server. Slack: https://cyclonedx.slack.com/archives/C04NFFE1962
jrnl - Quick and easy CLI journaling tool for Github wiki journals.
clair - Vulnerability Static Analysis for Containers
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
falco - Cloud Native Runtime Security
pyroscope - Continuous Profiling Platform. Debug performance issues down to a single line of code [Moved to: https://github.com/grafana/pyroscope]
lynis - Lynis - Security auditing tool for Linux, macOS, and UNIX-based systems. Assists with compliance testing (HIPAA/ISO27001/PCI DSS) and system hardening. Agentless, and installation optional.