jupyter/community-committee#

documentation · owned by Jupyter Community Building · on GitHub · scanned at commit e913c15

Reach#

  • Packages: none

  • Container images: none

  • Run by other repositories: none

  • Live service: jupyter.org/community-committee

  • Security boundary: no

  • Why these labels: The repo contains only Markdown/docs, meeting notes, charter, and configs for building a MyST website; the README states it is a ‘team compass’ for community alignment. (deepseek-v4-pro)

Security topics#

CI and releases#

  • Workflows: 3, run on issue_comment, pull_request_target, push, schedule, workflow_dispatch

  • Publishes: website

  • Secrets: HACKMD_TOKEN

  • Actions: 6, 5 by tag, 1 by branch. Third-party, not pinned: mfisher87/hackmd-meeting-notes-action@main, prefix-dev/setup-pixi@v0.8.8, readthedocs/actions@v1

  • Build requirements: none

Details#

  • All actions it uses: actions/checkout@v4, actions/deploy-pages@v4, actions/upload-pages-artifact@v3, mfisher87/hackmd-meeting-notes-action@main, prefix-dev/setup-pixi@v0.8.8, readthedocs/actions@v1

  • Files: 51: 39 docs, 8 config, 3 other, 1 web