January 2018 Summaries

The article emphasizes the importance of building developer tools that handle security instead of traditional security tools designed for developers. This approach focuses on the developer's needs, reframes security as a supporting function, and integrates security into the development process. By doing so, it can reduce the chance of an outage, improve communication and collaboration across teams, and empower junior developers to take on bigger tasks. The article also highlights the need to replace existing security tools with ones that mimic successful developer tools, such as APM tools, linters, and code review tools, which have already gained traction among developers. By adopting this approach, it's possible to increase adoption and make security a natural part of the development process.

The Snyk API allows developers to retrieve project issues and vulnerabilities associated with their projects, providing visibility into vulnerability status within existing portals and workflows. To access the API, customers must be on a paid plan, log in or sign up for an account, and obtain an API key. The API endpoints include `orgs`, `projects`, and `issues`, which can be used to fetch lists of organizations, projects, and issues, respectively. By using the `aggregated-issues` endpoint, developers can retrieve a JSON payload containing vulnerabilities, licenses, and other information about each issue. This data can be filtered by severity, type, and other criteria, and can be displayed in various formats using tools like jq. The Snyk API also provides a reporting API for more advanced use cases, such as charting issues over time or having more powerful filtering capabilities.