lineage-pii-and-governance — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited lineage-pii-and-governance (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Governance is an engineering concern, not a cleanup exercise. This skill ensures that every meaningful data change accounts for ownership, lineage, access, and sensitive-data handling before release.
Every published dataset should have:
Determine whether fields are:
Controls may include:
Record how the data flows from source to publish layer, including major transformations.
Do not stop at documentation. Check that access and masking rules are actually reflected in code or platform configuration.
| Rationalization | Reality |
|---|---|
| "It is only internal data." | Internal datasets still create exposure, misuse, and compliance risk. |
| "We will document lineage later." | Lineage that is not updated during change work becomes stale immediately. |
| "Security will handle masking downstream." | Sensitive data should be controlled as close to production as possible. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.