active 2023-11-19 → 2023-11-19 (UTC)
Partial coverage20,503 / 26,259 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-15 → 2026-08-13 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
151
Pushes
0
Pull requests
0
Issues
150
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 1 days from 2023-11-19 to 2023-11-19. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 150 total, peak 150 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| vvcb | 150 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#150vvcb2023-11-19 11:164.4.1.:You must ensure that all projects using your TRE are aware of any associated costs and are able and willing to pay them.
- Issue#149vvcb2023-11-19 11:164.3.3.:You should periodically carry out a training needs analysis (TNA) for all stakeholders included within your TRE provision.
- Issue#148vvcb2023-11-19 11:164.3.2.:You should have an education programme in place to upskill stakeholders in the use and management of your TRE.
- Issue#147vvcb2023-11-19 11:154.3.1.:You must document all features of your TRE implementation.
- Issue#146vvcb2023-11-19 11:154.2.2.:You should not give project managers direct access to the TRE.
- Issue#145vvcb2023-11-19 11:154.2.1.:You should ensure that all projects using your TRE have a named project manager.
- Issue#144vvcb2023-11-19 11:154.1.2.:You should regularly test the aspects of your business continuity plan concerning TREs, and have a process in place to iterate the plan if required.
- Issue#143vvcb2023-11-19 11:154.1.1.:You should have a business continuity plan that includes consideration of loss of service for deployed TREs.
- Issue#142vvcb2023-11-19 11:073.3.3.:You must have a documented process for disclosure control of outputs from the TRE.
- Issue#141vvcb2023-11-19 11:073.3.2.:You should establish the intended outputs of each project from the outset.
- Issue#140vvcb2023-11-19 11:073.3.1.:You should have a system to help classify outputs.
- Issue#139vvcb2023-11-19 11:063.2.6.:You could restrict access to particular networks or physical locations.
- Issue#138vvcb2023-11-19 11:063.2.5.:You could use federated authentication or single sign-on (SSO) for user login.
- Issue#137vvcb2023-11-19 11:063.2.4.:You must ensure that multi-factor authentication is enabled for all users.
- Issue#136vvcb2023-11-19 11:063.2.3.:You must restrict a user’s access to only data required in their work.
- Issue#135vvcb2023-11-19 11:063.2.2.:You must be reasonably convinced of the identity of each person being granted an account.
- Issue#134vvcb2023-11-19 11:063.2.1.:You must not create user accounts for use by more than one person.
- Issue#133vvcb2023-11-19 11:063.1.13.:Data held within the TRE should be the minimum required for analysis or research.
- Issue#132vvcb2023-11-19 11:063.1.12.:You must, to a reasonable extent, prevent unauthorised data ingress or egress.
- Issue#131vvcb2023-11-19 11:063.1.11.:You should log how input data is modified.
- Issue#130vvcb2023-11-19 11:063.1.10.:You should have a method of providing proof of deletion/removal of files.
- Issue#129vvcb2023-11-19 11:053.1.9.:You must have a policy on data deletion.
- Issue#128vvcb2023-11-19 11:053.1.8.:You must keep a record of what data your TRE holds.
- Issue#127vvcb2023-11-19 11:053.1.7.:Your data egress process could sometimes require project-independent approval.
- Issue#126vvcb2023-11-19 11:053.1.6.:Egress must be limited to the information asset owners or their delegates.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.