Snyk Projects now stay in sync with repository content
Snyk now automatically keeps your Projects synchronized with repository changes. When files are added, moved, or deleted in monitored branches, Snyk automatically creates or deactivates corresponding Projects, eliminating the need for manual re-imports.
The "What"
Repo Content Sync keeps your Snyk Projects aligned with what your repositories actually contain. When a change is merged to a branch Snyk monitors, Snyk creates and begins monitoring Projects for newly added manifest, Dockerfile, and configuration files, and deactivates the Projects whose files were removed. A file that is moved or renamed is picked up at its new path, and the Project at the old path is deactivated. Until now, keeping Snyk in step with a repository was a manual step: someone re-imported the repository, or a newly added dependency file simply went unscanned. Repo Content Sync makes repository content itself the trigger, so your Project list reflects the code as it is today rather than as it was at import. Sync covers Code, open source, secrets, infrastructure as code, and container (Dockerfile) Projects, and it works on custom branches as well as default branches.
Repo Content Sync will be rolled out gradually over the next several weeks.
Source: original entry ↗
More from Snyk
Follow Snyk to get its new changes in your feed and email digest.
Snyk CLI v1.1308.1 released
HTML report output is now available by default without preview features, and project names are consistently displayed in test summaries. This release also patches multiple security vulnerabilities.
Pending ignore requests now visible on Project's Issues page
Issues with pending ignore requests now display a clear "Pending Ignore Request" status on the Issues page and in issue details, with filtering support. The issues API now reports pending as part of an issue's ignore status for programmatic distinction of open, pending, and ignored findings.
Snyk Code October update: improved analysis and more findings
Snyk Code now analyzes projects more deeply and accurately across Java, Kotlin, Go, TypeScript, JavaScript, Python, C#, PHP and Ruby, with significantly more findings reported. Improvements include better import resolution via config files, corrected PHP typing, expanded library coverage, new vulnerability detection rules, and enhanced template and serverless application analysis.