Security

Security audits, vulnerabilities, compliance, auth, secrets, and safe automation

skills in category: 28,990
pages available: 1,208

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse security skills

Showing 1,201–1,224 of 28,990 skills

Aas Secure Delivery Security Header Completeness ReconciliationAUse when the web response security header regression workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the response-header comparison with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Closeout Handoff LedgerAUse when a web response security header regression work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the response-header comparison with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and writ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect web response security header regression to produce a before/after change record and impact map for the response-header comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write capabilities only when rel...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Security Header Approval Evidence PacketAUse when a web response security header regression result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the response-header comparison containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Threshold Rule CheckAUse when a API request signing canonicalization decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the request-signing interoperability fixture showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Source Provenance LedgerAUse when a decision about API request signing canonicalization depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the request-signing interoperability fixture. Success means each material claim has a source, version/date, location, and confidence note; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Scope Intake GateAUse when a new API request signing canonicalization request needs a bounded work scope to produce a scoped intake card for the request-signing interoperability fixture. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refin...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Scenario Sensitivity MatrixAUse when the API request signing canonicalization team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the request-signing interoperability fixture with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, an...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Recovery Readiness DrillAUse when the API request signing canonicalization workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the request-signing interoperability fixture with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, ...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Exception Triage QueueAUse when the API request signing canonicalization workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the request-signing interoperability fixture with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, te...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Completeness ReconciliationAUse when the API request signing canonicalization workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the request-signing interoperability fixture with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Closeout Handoff LedgerAUse when a API request signing canonicalization work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the request-signing interoperability fixture with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, tes...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect API request signing canonicalization to produce a before/after change record and impact map for the request-signing interoperability fixture. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, and write capabilities on...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Request Signing Approval Evidence PacketAUse when a API request signing canonicalization result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the request-signing interoperability fixture containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fe...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Threshold Rule CheckAUse when a CI workload identity federation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the workload-identity trust review showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetc...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Source Provenance LedgerAUse when a decision about CI workload identity federation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the workload-identity trust review. Success means each material claim has a source, version/date, location, and confidence note; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Scope Intake GateAUse when a new CI workload identity federation request needs a bounded work scope to produce a scoped intake card for the workload-identity trust review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Scenario Sensitivity MatrixAUse when the CI workload identity federation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the workload-identity trust review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, a...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Recovery Readiness DrillAUse when the CI workload identity federation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the workload-identity trust review with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read,...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Exception Triage QueueAUse when the CI workload identity federation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the workload-identity trust review with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, t...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Completeness ReconciliationAUse when the CI workload identity federation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the workload-identity trust review with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, rea...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Closeout Handoff LedgerAUse when a CI workload identity federation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the workload-identity trust review with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, te...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect CI workload identity federation to produce a before/after change record and impact map for the workload-identity trust review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, and write capabilities o...securityrustgoVotes: 0GitHub stars: 2
Aas Secure Delivery Oidc Federation Approval Evidence PacketAUse when a CI workload identity federation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the workload-identity trust review containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, f...securityrustgoVotes: 0GitHub stars: 2