The safeguards map / 3.7 Admission and owner settings

gittuf

Open Source Security Foundation (foundation). OpenSSF, incubating. Apache-2.0. Mapped; as of .

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

A Git security system that lets repository maintainers set policies on who may change which references, and lets any developer verify independently that changes followed them.

Where it sits

3.7 Admission and owner settings (primary): Holds policy rules for a Git repository's references and files and verifies that changes followed those rules, independently of the hosting forge.

gittuf is a platform-agnostic Git security system.

captured

any developer can independently verify that a repository’s changes followed the expected security policies

captured

gittuf allows for verifying rules for Git references and files.

captured

gittuf allows users to specify rules in one or more policy files.

captured

Facts

Concern
security
Names the law
no
Subject
software
Used by
those who make itthose who run it
Runs
by handin CI
Policy comes from
owner-entered settings

Handoffs

None recorded. A mapped entry with no handoff is here for its foundation home.

Collector's note

The project's own README calls it beta software. Its rules are signed metadata in the repository, not an external Rego or Cedar bundle.

Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.