jupyterhealth/jupyterhealth-demo-deploy#
Deployment configuration for JupyterHealth demo at Berkeley
deployment · owned by JupyterHub and Binder · on GitHub · scanned at commit b0dfebb
Reach#
Packages: none
Container images: none
Run by other repositories: none
Live service: JupyterHealth demo at Berkeley
Security boundary: no
Why these labels: Contains Kubernetes deployment configs (charts, cluster configs), CI deploy workflow, and secrets managed via SOPS; README explicitly states ‘Deployment configuration for JupyterHealth demo at Berkeley’. (deepseek-v4-pro)
Security topics#
zizmor: done via pre-commit. Pre-commit hook, and CI runs pre-commit. Files: .pre-commit-config.yaml
SECURITY.md: n/a. Ships no package or image.
PyPI attestations: n/a. No PyPI package.
npm trusted publishing: n/a. No npm package.
Supported Python: n/a. No PyPI package.
Owner: done. Owned by JupyterHub and Binder.
CI and releases#
Workflows: 2, run on pull_request, push
Publishes: cloud
Secrets: none
Actions: 5, all pinned to a commit
Build requirements: none
Details#
All actions it uses: actions/checkout@3d3c42e, actions/setup-python@6d4fd22, aws-actions/configure-aws-credentials@e125382, azure/setup-helm@9bc31f4, step-security/mozilla-sops-action@96171ff
Files: 34: 26 config, 4 other, 2 docs, 2 code