As senior engineers evaluate open-source tools for generating Software Bill of Materials (SBOM), a comparison between anchore/syft and aquasecurity/starboard reveals distinct differences in momentum, community size, and use cases. Anchore/syft, with 8,568 stars and a notable 117 stars added in the last 30 days, demonstrates strong momentum and a sizable community. This tool's versatility in handling both container images and filesystems makes it broadly applicable for SBOM generation across various deployment scenarios, from cloud-native applications to traditional infrastructure. In contrast, aquasecurity/starboard, now superseded by aquasecurity/trivy-operator, shows significantly less community engagement with 1,372 stars and only 2 additional stars in the last 30 days, indicating a stalled momentum. Originally designed for Kubernetes-native security, its use cases were more specialized compared to syft, focusing on integrated security scanning within Kubernetes environments. The project's supersession suggests a shift in the maintainers' focus towards the trivy-operator, which may offer more integrated capabilities but requires evaluation on its own merits. Both projects cater to different needs: syft for general-purpose SBOM generation and starboard (historically) for Kubernetes-centric security and compliance. Engineers should consider these factors when selecting a tool that aligns with their specific requirements and preferred community engagement level.