workfront-approvals-api — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited workfront-approvals-api (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.
Specialist for the Workfront Universal Approval Service (UAS) — document-only review and approval workflows. Knows the UAS API structure, authentication requirements, approval status model, participant roles, decision values, template usage, and multi-stage workflows. The UAS is separate from both the standard Workfront REST API and the legacy work item approval system.
| Task | Load |
|---|---|
| Understand the UAS system, objects, auth, and scope | UNIVERSAL_APPROVAL_SERVICE_OVERVIEW.md |
| Create or update an approval, use templates, lock/unlock stages | UAS_TEMPLATES_AND_STAGES.md |
| Add or remove reviewers and approvers | UAS_PARTICIPANTS.md |
| Read or interpret approval status and decisions; make a decision | UAS_STATUS_AND_DECISIONS.md |
| Task | Load |
|---|---|
| Understand object approval workflows, supported objects, fields | OBJECT_APPROVALS_OVERVIEW.md |
| Approve, reject, or recall an approval on a project/task/issue | OBJECT_APPROVALS_ACTIONS.md |
| Find approval process IDs, attach processes, query approver status | OBJECT_APPROVALS_PROCESSES.md |
Skip any file below that does not exist in this project — not all projects use all layers.
docs/design-principles/ exists)docs/design-principles/architecture.md — approved patterns, banned patterns; read before any structural decisiondocs/design-principles/backend.md — handler structure, error patterns, service boundaries; read before writing implementation codedocs/impl-log/ exists)Before implementing:
docs/impl-log/backend/index.md — current backend state (required before writing new code)docs/impl-log/backend/log.md header lines — prior decisions relevant to this taskAt task completion:
docs/impl-log/backend/index.md in-place to reflect new current statedocs/impl-log/backend/log.mdDOCV) approvals only; project/task/issue approvals use the legacy system/attask/api/)NEEDS_WORK > APPROVED_WITH_CHANGES > APPROVED)APPROVED_WITH_CHANGES decision is NOT supported in the Frame.io integrationDocument approvals (UAS):
| Task | Load |
|---|---|
| UAS overview, objects, base URL, auth | UNIVERSAL_APPROVAL_SERVICE_OVERVIEW.md |
| Create or update an approval, templates, lock/unlock | UAS_TEMPLATES_AND_STAGES.md |
| Add/remove reviewers and approvers | UAS_PARTICIPANTS.md |
| Approval status values, decision rollup, make a decision | UAS_STATUS_AND_DECISIONS.md |
Object approvals (projects/tasks/issues):
| Task | Load |
|---|---|
| How object approvals work, supported objects | OBJECT_APPROVALS_OVERVIEW.md |
| approveApproval / rejectApproval / recallApproval actions | OBJECT_APPROVALS_ACTIONS.md |
| Approval process IDs, attach processes, approver status | OBJECT_APPROVALS_PROCESSES.md |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.