Repository navigation
Code security transaction report in PDF #781
Description
Activity
- locked and limited conversation to collaborators
on May 12, 2023 - moved this from Q2 2023 – Apr-Jun to Q4 2023 – Oct-Dec in GitHub Public Roadmap
on May 12, 2023 - moved this from Q4 2023 – Oct-Dec to Q1 2024 – Jan-Mar in GitHub Public Roadmap
on Jun 20, 2023 - moved this from Q1 2024 – Jan-Mar to Q3 2024 – Jul-Sep in GitHub Public Roadmap
on Apr 19, 2024 - changed the title
[-]Code security transaction report in CSV and PDF formats[/-][+]Code security transaction report in PDF[/+]on Apr 19, 2024 With our exciting roadmap ahead, we've made the tough decision to deprioritize this feature to focus on higher-impact projects. If you’re interested in this feature, please share your feedback in the GitHub community so we can track interest and consider it in the future.
We wanted to provide more details on why we removed this from the roadmap. We are currently focusing on other features. This has been removed from the roadmap for now, and we will revisit it once we can provide a more accurate delivery estimate.
If you’re interested in this feature, please share your feedback in the GitHub community so we can track interest and consider it in the future.
Summary
This feature enables you to generate a report of security alerts occurring during a specified period and export the results in PDF format.
Intended Outcome
Enterprise users must comply with strict security regulations that require producing transactional reports of security alerts. The reports must meet specific requirements and, generally, must be generated by the security vendor directly. This feature streamlines the compliance reporting process, enabling users to generate reports that meet regulatory standards.
How will it work?
You will be able to specify a reporting period and generate a report of security alerts that occurred during that period. The report will be able to be generated in PDF format.