Sweden

sweden is the facade for a security-first Rust ecosystem for lawful, typed access to Swedish public APIs and datasets. Shared logic is dependency-free, no_std, and independently publishable. Future agency crates remain no_std; future networking is isolated in focused std crates and is never enabled by default.

The repository is at its 0.1.0 foundation. It contains only the two crates needed now: sweden-core and the sweden facade. It does not yet make real upstream requests, and no agency integration has been introduced.

Install

The default facade exposes only sweden-core:

[dependencies]
sweden = "0.1.0"

Or depend directly on the foundation crate:

[dependencies]
sweden-core = "0.1.0"

Current Status

Workspace

No empty placeholder crate is published. A crate is created and published only when its implementation begins:

Every Rust crate introduced by this project is published to crates.io. Agency crates depend on sweden-core, never on the root facade or on one another.

Crate Versioning And Publication

The sweden facade always equals the repository tag and is published for every release. Subcrates use independent versions and are published only when their code, bugfixes, dependency requirements, or immutable package metadata change. Unchanged subcrates keep their last crates.io version.

At v1.0.0, every crate then present in the workspace converges to 1.0.0 and is published. The exact per-crate state is tracked in the crate version matrix and enforced by scripts/release_crates.py.

Rust Compatibility

Rust 1.97.1 is the pinned development and release toolchain. The public crates support every stable Rust release from 1.90.0 through 1.97.1.

The latest-stable pin and Cargo tool versions are checked by scripts/check_latest_tools.sh before a release.

Platform Direction

Pure library crates are designed from day one for Linux, Windows, macOS, FreeBSD, NetBSD, Android, and iOS. Platform-independent code does not assume Unix paths, sockets, clocks, or environment variables. A future Aesynx transport can be added behind the same transport contracts without changing agency crates.

no_std support does not claim that TLS, DNS, or sockets are platform independent. Applications provide those facilities through an explicit transport implementation.

Security

The repository starts fail-closed:

• no third-party project dependencies;
• no default networking, TLS, credentials, filesystem, clock, or telemetry;
• no arbitrary host or generic proxy surface;
• no unsafe Rust;
• explicit response budgets;
• source integrations stay Foundation until their policy, fixtures, tests, upstream review, security review, and pentest gates pass;
• CodeQL uses GitHub default setup rather than an advanced workflow;
• non-generated Rust files over 500 lines fail the local gate.

Report vulnerabilities privately as described in the security policy.

Development

Run the normal local gate:

scripts/checks.sh

Run the networked freshness and release gate only when preparing a release:

scripts/release_0_1_gate.sh

No tag is created when implementation finishes. Every version stops for the maintainer's pentest. Findings, fixes, retests, and later GitHub CI fixes stay current in the same versioned repository report. The implementation and AWAITING PENTEST report are committed as the exact pentest baseline. The pentest outcome and any remediation are committed next; tagging happens only after the maintainer confirms GitHub is green and explicitly requests the tag.

After that requested tag exists at HEAD, publish only the planned crates in dependency order:

scripts/release_crates.py --check
scripts/release_crates.py --version 0.1.0 --require-tag

Documentation

• Implementation plan
• Release plan
• Crate version matrix
• Initial architecture discussion
• Modularity policy
• Toolchain policy
• Threat model
• Security controls
• Supply-chain security
• Unsafe policy

License

Licensed under either the Apache License, Version 2.0 or the MIT license, at your option.