cargo-caps 0.0.2

Audit what a crate is capable of by analyzing what linker symbols it emits
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50

use std::fs;
use std::path::Path;

use anyhow::Context as _;

#[derive(clap::Args)]
pub struct InitCommand;

impl InitCommand {
    #[expect(clippy::unused_self)]
    pub fn execute(self) -> anyhow::Result<()> {
        let config_path = Path::new("cargo-caps.eon");

        if config_path.exists() {
            anyhow::bail!("cargo-caps.eon already exists");
        }

        let default_config = r#"// Configuration file for cargo-caps.
// See https://crates.io/crates/cargo-caps
// The capabilities are additive:
// if a crate matches several rules, the crate is granted
// the union of the capabilities afforded by all the rules.
rules: [
	{
		// Capabilities all crates are allowed:
		crates: ["*"]
		caps: [
            "alloc"   // allocate memory
            "panic"   // call `panic!()`
            "stdio"   // Read/write stdin/stdout/stderr
            "sysinfo" // Read ystem info like env-vars
            "time"    // Tell the time
        ]
	}
	{
		// These crates are allowed to have build.rs files
		caps: ["build.rs"]
		crates: []
	}
]
"#;

        fs::write(config_path, default_config)
            .with_context(|| "Failed to create cargo-caps.eon file")?;

        println!("Created cargo-caps.eon");
        println!("Try running 'cargo-caps check'");
        Ok(())
    }
}