Compile workflow

[BillBensing]

No description provided.

[dryrunsecurity]

DryRun Security Summary

The pull request covers changes to various files, including the .gitignore, Cargo.toml, Makefile, GitHub Actions workflow, and several test files, with a focus on renaming the collection-cli application to nape-cli, improving the build process, and implementing secure assurance report functionality.

Expand for full summary

Summary:

The changes in this pull request cover a variety of files, including the .gitignore, Cargo.toml, Makefile, GitHub Actions workflow, and several test files. The key changes are:

1. .gitignore: The addition of the .DS_Store file to the .gitignore file is a standard and recommended practice to prevent the accidental inclusion of these macOS-specific files in the Git repository.

2. Cargo.toml: The changes involve renaming the collection-cli application to nape-cli within the Rust workspace. This is a structural change that should be reviewed to ensure that the new application does not introduce any new dependencies or security vulnerabilities.

3. Makefile: The changes focus on the build process, including the addition of a new "ma-release-build" target. While these changes do not directly introduce security concerns, it's important to review the overall build process to ensure that it follows secure practices, such as dependency management, testing, and secure deployment.

4. GitHub Actions Workflow: The new nape-cli-release-workflow.yaml file introduces a workflow that checks the version change and triggers the compilation and release of the NAPE CLI application. This workflow has a strong focus on security, including version validation, conditional execution, and restricted triggers.

5. Test Files: The changes in the test files, such as v1_0_0_tests.rs and persist_report_gateway_tests.rs, demonstrate the implementation of assurance report functionality, including the use of cryptographic hashes, detailed assurance activities, and traceability metadata. These changes help ensure the integrity and trustworthiness of the assurance reporting process.

Files Changed:

1. .gitignore: The addition of the .DS_Store file to the .gitignore file is a standard and recommended practice.
2. Cargo.toml: The changes involve renaming the collection-cli application to nape-cli within the Rust workspace.
3. Makefile: The changes focus on the build process, including the addition of a new "ma-release-build" target.
4. .github/workflows/nape-cli-release-workflow.yaml: This new workflow checks the version change and triggers the compilation and release of the NAPE CLI application.
5. apps/nape-cli/Cargo.toml: The changes reflect the renaming of the Rust package from "nape_collection_cli" to "nape_cli".
6. apps/nape-cli/src/gateway_adapter/serde/specification_serializer/assurance_report/v1_0_0_tests.rs: This test case verifies the serialization and deserialization of an assurance report.
7. apps/nape-cli/src/gateway_adapter/serde/persist_report_gateway_tests.rs: These changes focus on the persistence of an Assurance Report in YAML format.

Code Analysis

We ran 9 analyzers against 30 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.