drjones/discord-tooling-collection
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Stewardship Readiness Checklist #1

New Issue
Open
opened 2026-05-20 17:09:54 -07:00 by drjones · 0 comments
drjones commented 2026-05-20 17:09:54 -07:00
Owner
Copy Link

Stewardship Readiness Checklist

Repo-Specific Decision

  • Status: BLOCKED: artifact provenance
  • Kind: automation
  • Visibility: private
  • Archived: no
  • Source files in Gitea head: 45
  • Mapped local source: discored raper (160 files scanned)

Concrete Blockers

  • High-confidence credential findings after remediation: 0
  • Generic secret-like findings needing review: 6
  • Release-blocking binary/archive artifacts: 1
  • Nested Git/gitlink entries: 6
  • License status: status-file-only-or-present

Next Actions

  • Review 6 generic secret-like findings and redact or mark false positive.
  • Resolve license/provenance before adding a final LICENSE.
  • Move or document 1 binary/archive artifacts before release.
  • Finish submodule/mirror decision for nested Git content.
  • Add real CI from detected manifests.

CI Recommendation

  • Node CI: install dependencies with detected package manager, run lint/test/build scripts when present.
  • Python CI: create venv, install deps, run pytest/ruff/mypy only if configured.
  • Go CI: go test ./... and go vet ./....

Notes

This issue is based on the repo-specific deep audit after credential remediation. Do not close it with generic documentation work; close it only after the blockers above are handled or explicitly marked not applicable.

# Stewardship Readiness Checklist ## Repo-Specific Decision - Status: **BLOCKED: artifact provenance** - Kind: `automation` - Visibility: `private` - Archived: `no` - Source files in Gitea head: 45 - Mapped local source: `discored raper` (160 files scanned) ## Concrete Blockers - High-confidence credential findings after remediation: 0 - Generic secret-like findings needing review: 6 - Release-blocking binary/archive artifacts: 1 - Nested Git/gitlink entries: 6 - License status: status-file-only-or-present ## Next Actions - [ ] Review 6 generic secret-like findings and redact or mark false positive. - [ ] Resolve license/provenance before adding a final LICENSE. - [ ] Move or document 1 binary/archive artifacts before release. - [ ] Finish submodule/mirror decision for nested Git content. - [ ] Add real CI from detected manifests. ## CI Recommendation - [ ] Node CI: install dependencies with detected package manager, run lint/test/build scripts when present. - [ ] Python CI: create venv, install deps, run pytest/ruff/mypy only if configured. - [ ] Go CI: `go test ./...` and `go vet ./...`. ## Notes This issue is based on the repo-specific deep audit after credential remediation. Do not close it with generic documentation work; close it only after the blockers above are handled or explicitly marked not applicable.
drjones added this to the Triage milestone 2026-05-20 17:09:54 -07:00
drjones added the docssecurityneeds-triageprovenance labels 2026-05-20 17:09:54 -07:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
blocked
Blocked by missing info, dependency, or decision
 bug
Something is broken or regressed
 docs
Documentation, README, wiki, or examples
 duplicate
Duplicate of another issue or repo task
 firmware
Embedded firmware source, builds, and release artifacts
 hardware
Boards, wiring, flashing, firmware, or physical setup
 needs-triage
Needs maintainer review and classification
 provenance
Origin, hashes, licensing, or artifact traceability
 release-ready
Ready for release or release review
 security
Security policy, safety boundary, or vulnerability handling
 upstream
Depends on or tracks an upstream project
No Label docs needs-triage provenance security
Milestone
No items
No Milestone Triage
Projects
Clear projects
No project
Assignees
Clear assignees
drjones
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: drjones/discord-tooling-collection#1
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?