cps-transparency-and-data — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cps-transparency-and-data (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.
CPS enforces political-science replication norms. Papers presenting quantitative analyses will not be granted final acceptance until replication materials (data, code, log files, etc.) are deposited at the CPS Dataverse on Harvard Dataverse, and every paper needs a data availability statement. Build the package as you go so final acceptance does not stall — and follow DA-RT-style transparency for qualitative evidence too.
log files, and documentation — at the CPS Dataverse on Harvard Dataverse (`dataverse.harvard.edu/dataverse/cps`). This gates final acceptance**, not post-publication.
where, and — if available but not shared — why not.
and figures: master script + README + pinned versions + seeds.
the journal editorial office**; explain the restriction and document how others can obtain the data.
supplementary material; the journal provides it to reviewers on request. Mark registered vs. exploratory analyses.
tables or active citation. Where confidentiality requires it, use controlled access (e.g., QDR).
Choose the transparency route before drafting the data availability statement:
| Evidence type | Default posture | Documentation to include |
|---|---|---|
| Cross-national public datasets | Share constructed data and code; cite original sources | Source versions, merge keys, transformations, and exact download dates |
| Proprietary/admin data | Share code, synthetic or redacted extracts where allowed, and access instructions | License limits, access route, variable construction, and verification path |
| Interviews/fieldnotes | Protect identities; share protocols, coding scheme, and evidence table when ethical | Consent limits, anonymization method, and claim-to-evidence map |
| Text corpus/web data | Share corpus identifiers or permissible text, plus scraping/cleaning code | Collection date, inclusion rules, deduplication, language processing decisions |
| Pre-analysis plan | Submit anonymized plan as supplement when used | Registered vs. exploratory analyses marked in manuscript and code |
The data availability statement should mirror the table: what is shared, where, what is restricted, and how a qualified reader can audit the claim without violating law, ethics, or provider terms.
renv.lock / requirements.txt / recorded installs)【Repository】CPS Dataverse (Harvard) — package staged? [Y/N]
【Reproduces tables/figures?】master script verified locally? [Y/N]
【Data availability statement】drafted? available where / why not?
【Documentation】README + provenance + seeds + pinned versions? [Y/N]
【Sharing posture】public / proprietary-admin / interview-fieldnote / text-corpus / PAP route chosen
【Restricted data?】explanation + access path + editorial-office note?
【Qualitative transparency】sources/evidence documented? [Y/N/NA]
【Pre-analysis plan】anonymized + registered/exploratory marked? [Y/N/NA]
【Next】cps-review-process../../resources/official-source-map.md — CPS data policy + CPS Dataverse URL../../resources/external_tools.md — reproducibility tooling and qualitative-transparency options (QDR)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.