Skip to content

Commit e19ec26

Browse files
committed
Create README.md
Signed-off-by: Andres Vega <av@messier42.com> Signed-off-by: Andrés Vega <av@messier42.com>
1 parent 7c9198b commit e19ec26

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

palantir/README.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
# Palantir (Project Adopter)
2+
3+
Palantir uses in-toto to protect the integrity of software from source to deployment across a large, heterogeneous environment.
4+
5+
## Highlights
6+
- **Multi-ecosystem builds:** Custom tooling emits signed attestations across Gradle, Godel, containers, Helm, and frontend bundles.
7+
- **Verifiable provenance:** Release and build steps produce attestations binding source commits/tags to produced artifacts.
8+
- **Enterprise distribution:** Attestations are packaged with artifacts and stored in existing artifact repositories, supporting disconnected/offline installs.
9+
- **Layered verification:** Verification occurs at publication and again at install time to guard against tampering in transit.
10+
- **Operational rollout:** Gradual enforcement with exemptions and controlled overrides ensured continuity for mission-critical services.
11+
- **Spec alignment:** Migration to in-toto v1 (with SLSA build attestations) simplified verification and improved performance at scale (e.g., reducing P99 verification spikes from ~90 minutes to <15).
12+
13+
## Reference
14+
[How Palantir Mastered In-Toto](https://blog.palantir.com/how-palantir-mastered-in-toto-b8a7107371bb)” (Medium, Sep 2025).

0 commit comments

Comments
 (0)