google / google/stellar-engine

[Feature Request] Implement a Security Linter

Open
#10 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
HCL
Stars
49
Forks
20
Avg merge
3d 14h
Merged PRs (30d)
28

Description

Description
Stellar Engine provides a secure foundation that our delivery teams, partners, and customers customize to meet specific needs. To help scale our best practices during this critical delivery phase (and beyond), we propose implementing an automated security linter in the CI/CD pipeline.

This linter will function as a codified, blameless guardrail. It will provide instant, automated feedback to engineers during customization, making it easy to apply our security principles consistently. The goal is to empower our delivery teams and customers to build and modify solutions with confidence, ensuring every deployment is hardened by default.

Justification
This initiative is a direct investment in delivery velocity and reliability. By automating our security expertise, we reduce manual review toil and systematically eliminate entire classes of configuration errors before they are in production.

Success Criteria

- A Pull Request violating a linter rule will be blocked with clear, actionable feedback.

- The linter successfully detects and blocks a core set of high-priority misconfigurations.

- The framework is extensible, allowing for new security checks to be added as our best practices evolve.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.