timetracker

Projects that follow the best practices below can voluntarily self-certify and show that they've achieved an Open Source Security Foundation (OpenSSF) best practices badge.

There is no set of practices that can guarantee that software will never have defects or vulnerabilities; even formal methods can fail if the specifications or assumptions are wrong. Nor is there any set of practices that can guarantee that a project will sustain a healthy and well-functioning development community. However, following best practices can help improve the results of projects. For example, some practices enable multi-person review before release, which can both help find otherwise hard-to-find technical vulnerabilities and help build trust and a desire for repeated interaction among developers from different companies. To earn a badge, all MUST and MUST NOT criteria must be met, all SHOULD criteria must be met OR be unmet with justification, and all SUGGESTED criteria must be met OR unmet (we want them considered at least). If you want to enter justification text as a generic comment, instead of being a rationale that the situation is acceptable, start the text block with '//' followed by a space. Feedback is welcome via the GitHub site as issues or pull requests There is also a mailing list for general discussion.

We gladly provide the information in several locales, however, if there is any conflict or inconsistency between the translations, the English version is the authoritative version.
If this is your project, please show your baseline badge status on your project page! The baseline badge status looks like this: Baseline badge level for project 11719 is baseline-1 Here is how to embed the baseline badge:
You can show your baseline badge status by embedding this in your markdown file:
[![OpenSSF Baseline](https://www.bestpractices.dev/projects/11719/baseline)](https://www.bestpractices.dev/projects/11719)
or by embedding this in your HTML:
<a href="https://www.bestpractices.dev/projects/11719"><img src="https://www.bestpractices.dev/projects/11719/baseline"></a>


These are the Baseline Level 2 criteria. These are criteria version v2026.08.28.

Baseline Series: Baseline Level 1 Baseline Level 2 Baseline Level 3

        

 Basics

  • General

    Note that other projects may use the same name.

    Simple time tracking front end with optional Jira synchronization, AD/LDAP integration and XLSX export.

    Please use SPDX license expression format; examples include "Apache-2.0", "BSD-2-Clause", "BSD-3-Clause", "GPL-2.0+", "LGPL-3.0+", "MIT", and "(BSD-2-Clause OR Ruby)". Do not include single quotes or double quotes.
    If there is more than one language, list them as comma-separated values (spaces optional) and sort them from most to least used. If there is a long list, please list at least the first three most common ones. If there is no language (e.g., this is a documentation-only or test-only project), use the single character "-". Please use a conventional capitalization for each language, e.g., "JavaScript".
    The Common Platform Enumeration (CPE) is a structured naming scheme for information technology systems, software, and packages. It is used in a number of systems and databases when reporting vulnerabilities.

 Controls 14/19 ●

  • Controls


    Not enough for a badge.

    When a CI/CD task is executed with no permissions specified, the CI/CD system MUST default the task's permissions to the lowest permissions granted in the pipeline. [OSPS-AC-04.01]
    Configure the project's settings to assign the lowest available permissions to new pipelines by default, granting additional permissions only when necessary for specific tasks.

    The repository's Actions setting 'Default workflow permissions' is currently set to 'Read and write permissions', so a job that omits a permissions block receives write access rather than the lowest permissions in the pipeline. All existing workflows do declare explicit minimal permissions (permissions: {} or contents: read), but the default itself is not restricted. Verified in the repository Actions settings on 2026-09-18. Switching the default to read-only is planned.


    Enough for a badge!

    When an official release is created, that release MUST be assigned a unique version identifier. [OSPS-BR-02.01]
    Assign a unique version identifier to each release produced by the project, following a consistent naming convention or numbering scheme. Examples include SemVer, CalVer, or git commit id.

    Every official release carries a unique semantic version identifier as a Git tag and GitHub Release (current: v6.3.4). See https://github.com/netresearch/timetracker/releases


    Enough for a badge!

    When an official release is created, that release MUST contain a descriptive log of functional and security modifications. [OSPS-BR-04.01]
    Ensure that all releases include a descriptive change log. It is recommended to ensure that the change log is human-readable and includes details beyond commit messages, such as descriptions of the security impact or relevance to different use cases. To ensure machine readability, place the content under a markdown header such as "## Changelog".

    Each GitHub Release contains hand-written notes structured into Highlights and Fixes, describing functional and security-relevant changes with references to the originating issues. See https://github.com/netresearch/timetracker/releases/tag/v6.3.4


    Enough for a badge!

    When a build and release pipeline ingests dependencies, it MUST use standardized tooling where available. [OSPS-BR-05.01]
    Use a common tooling for your ecosystem, such as package managers or dependency management tools to ingest dependencies at build time. This may include using a dependency file, lock file, or manifest to specify the required dependencies, which are then pulled in by the build system.

    Dependencies are ingested exclusively through standardized ecosystem tooling with committed lockfiles: Composer for PHP (composer.lock), Bun for the frontend (frontend/bun.lock), npm for E2E tooling (package-lock.json) and Docker/BuildKit for base images. CI installs with frozen lockfiles. See https://github.com/netresearch/timetracker/blob/main/.github/workflows/ci.yml


    Not enough for a badge.

    When an official release is created, that release MUST be signed or accounted for in a signed manifest including each asset's cryptographic hashes. [OSPS-BR-06.01]
    Sign all released software assets at build time with a cryptographic signature or attestations, such as GPG or PGP signature, Sigstore signatures, SLSA provenance, or SLSA VSAs. Include the cryptographic hashes of each asset in a signed manifest or metadata file.

    The SLSA provenance workflow runs only on 'release: published' and only when the release carries downloadable assets. Current releases ship no assets - the deliverable is the container image on ghcr.io - so no signed manifest of asset hashes is produced, and the container images themselves are not signed (no cosign step exists). A source-provenance.json is attached but is unsigned. See https://github.com/netresearch/timetracker/blob/main/.github/workflows/slsa-provenance.yml and https://github.com/netresearch/timetracker/releases/tag/v6.3.4


    Not enough for a badge.

    When the project has made a release, the project documentation MUST include a description of how the project selects, obtains, and tracks its dependencies. [OSPS-DO-06.01]
    It is recommended to publish this information alongside the project's technical & design documentation on a publicly viewable resource such as the source code repository, project website, or other channel.

    Dependency automation is configured (.github/dependabot.yml covering github-actions, composer, npm and bun; renovate.json), but the documentation does not describe how dependencies are selected, obtained and tracked as a policy. Adding this section to CONTRIBUTING.md or docs/ is planned.


    Enough for a badge!

    The project documentation MUST include instructions on how to build the software, including required libraries, frameworks, SDKs, and dependencies. [OSPS-DO-07.01]
    It is recommended to publish this information alongside the project's contributor documentation, such as in CONTRIBUTING.md or other developer task documentation. This may also be documented using Makefile targets or other automation scripts.

    Build instructions covering required runtimes, libraries and tooling are documented in README.md (Requirements and Quick Start, Docker and manual install) and docs/development.md, with a Makefile exposing the standard targets. See https://github.com/netresearch/timetracker/blob/main/docs/development.md


    Not enough for a badge.

    The project documentation MUST include a list of project members with access to sensitive resources. [OSPS-GV-01.01]
    Document project participants and their roles through such artifacts as members.md, governance.md, maintainers.md, or similar file within the source code repository of the project. This may be as simple as including names or account handles in a list of maintainers, or more complex depending on the project's governance.

    The project has no documented list of members with access to sensitive resources: there is no MAINTAINERS.md, no CODEOWNERS file and no named maintainers in CONTRIBUTING.md. Access is managed implicitly through Netresearch GitHub organization teams. Publishing an explicit maintainer list is planned.


    Enough for a badge!

    The project documentation MUST include descriptions of the roles and responsibilities for members of the project [OSPS-GV-01.02]
    Document project participants and their roles through such artifacts as members.md, governance.md, maintainers.md, or similar file within the source code repository of the project.

    CONTRIBUTING.md describes the roles and responsibilities in the project, including maintainer duties, reviewer expectations and the author/reviewer checklists applied to every change. See https://github.com/netresearch/timetracker/blob/main/CONTRIBUTING.md


    Enough for a badge!

    The project documentation MUST include a guide for code contributors that includes requirements for acceptable contributions. [OSPS-GV-03.02]
    Extend the CONTRIBUTING.md or CONTRIBUTING/ contents in the project documentation to outline the requirements for acceptable contributions, including coding standards, testing requirements, and submission guidelines for code contributors. It is recommended that this guide is the source of truth for both contributors and approvers.

    CONTRIBUTING.md is a full contributor guide stating the requirements for acceptable contributions: coding standards, commit message conventions, testing requirements with per-layer coverage targets, and documentation obligations. See https://github.com/netresearch/timetracker/blob/main/CONTRIBUTING.md


    Enough for a badge!

    The version control system MUST require all code contributors to assert that they are legally authorized to make the associated contributions on every commit. [OSPS-LE-01.01]
    Include a DCO in the project's repository, requiring code contributors to assert that they are legally authorized to commit the associated contributions on every commit. Use a status check to ensure the assertion is made. A CLA also satisfies this requirement. Some version control systems, such as GitHub, may include this in the platform terms of service.

    The probot DCO GitHub App (https://probot.github.io/apps/dco/) runs as a 'DCO' check on every pull request and fails unless every commit carries a Signed-off-by trailer matching its author, so contributors assert their legal authorisation under the Developer Certificate of Origin on each commit. The requirement is documented in CONTRIBUTING.md, and the DCO check is now configured as a required status check on main, so it blocks merging. The app is installed at the GitHub App level rather than as a workflow file. Example run: https://github.com/netresearch/timetracker/runs/105505933951


    Enough for a badge!

    When a commit is made to the primary branch, any automated status checks for commits MUST pass or be manually bypassed. [OSPS-QA-03.01]
    Configure the project's version control system to require that all automated status checks pass or require manual acknowledgement before a commit can be merged into the primary branch. It is recommended that any optional status checks are NOT configured as a pass or fail requirement that approvers may be tempted to bypass.

    Branch protection on 'main' now requires the status checks 'CI Success' and 'DCO' to pass before a change can be merged, with the strict policy enabled so branches must be up to date. 'CI Success' aggregates the frontend build, linting, unit, integration and E2E tests, static analysis and the dependency audits. Verified in the repository branch protection settings on 2026-09-18.


    Enough for a badge!

    Prior to a commit being accepted, the project's CI/CD pipelines MUST run at least one automated test suite to ensure the changes meet expectations. [OSPS-QA-06.01]
    Automated tests should be run prior to every merge into the primary branch. The test suite should be run in a CI/CD pipeline and the results should be visible to all contributors. The test suite should be run in a consistent environment and should be run in a way that allows contributors to run the tests locally. Examples of test suites include unit tests, integration tests, and end-to-end tests.

    The CI pipeline runs on every pull request and every push to main and executes frontend unit tests (Vitest), PHP unit and integration tests (PHPUnit, ~2,500 test methods), Playwright E2E tests across four shards, plus static analysis and architecture tests. See https://github.com/netresearch/timetracker/blob/main/.github/workflows/ci.yml


    Enough for a badge!

    When the project has made a release, the project documentation MUST include design documentation demonstrating all actions and actors within the system. [OSPS-SA-01.01]
    Include designs in the project documentation that explains the actions and actors. Actors include any subsystem or entity that can influence another segment in the system. Ensure this is updated for new features or breaking changes.

    Design documentation covers the actors and actions in the system: README.md contains the architecture overview, docs/security.md documents the role model, authentication and authorization flows including sequence diagrams, and 27 Architecture Decision Records under docs/adr/ record the design decisions. See https://github.com/netresearch/timetracker/tree/main/docs/adr and https://github.com/netresearch/timetracker/blob/main/docs/security.md


    Enough for a badge!

    When the project has made a release, the project documentation MUST include descriptions of all external software interfaces of the released software assets. [OSPS-SA-02.01]
    Document all software interfaces (APIs) of the released software assets, explaining how users can interact with the software and what data is expected or produced. Ensure this is updated for new features or breaking changes.

    External interfaces are documented: docs/api.md is a complete REST API reference, docs/configuration.md documents every environment variable, and the LDAP, Jira worklog/subticket and Personio integrations each have their own operator guide under docs/. See https://github.com/netresearch/timetracker/blob/main/docs/api.md


    Not enough for a badge.

    When the project has made a release, the project MUST perform a security assessment to understand the most likely and impactful potential security problems that could occur within the software. [OSPS-SA-03.01]
    Performing a security assessment informs both project members as well as downstream consumers that the project understands what problems could arise within the software. Understanding what threats could be realized helps the project manage and address risk. This information is useful to downstream consumers to demonstrate the security acumen and practices of the project. Ensure this is updated for new features or breaking changes.

    docs/security.md documents the security architecture, the implemented controls and a list of potential enhancements, and automated analysis runs continuously (CodeQL, PHPStan level 10, OpenSSF Scorecard, Dependabot). However, the project has no recorded threat model or structured security assessment that enumerates the most likely and most impactful potential security problems. Producing one is planned.


    Enough for a badge!

    The project documentation MUST include a policy for coordinated vulnerability disclosure (CVD), with a clear timeframe for response. [OSPS-VM-01.01]
    Create a SECURITY.md file at the root of the directory, outlining the project's policy for coordinated vulnerability disclosure. Include a method for reporting vulnerabilities. Set expectations for how the project will respond and address reported issues.

    SECURITY.md defines the coordinated vulnerability disclosure policy with explicit timeframes: acknowledgement within 48 hours, initial assessment within 5 business days, and credit to reporters in the release notes. See https://github.com/netresearch/timetracker/blob/main/SECURITY.md


    Enough for a badge!

    The project documentation MUST provide a means for private vulnerability reporting directly to the security contacts within the project. [OSPS-VM-03.01]
    Provide a means for security researchers to report vulnerabilities privately to the project. This may be a dedicated email address, a web form, VCS specialized tools, email addresses for security contacts, or other methods.

    Private vulnerability reporting via GitHub Security Advisories is enabled for the repository and is the documented reporting channel; public issues are explicitly excluded. Verified in the repository security settings on 2026-09-18. See https://github.com/netresearch/timetracker/security/advisories/new and https://github.com/netresearch/timetracker/blob/main/SECURITY.md


    Enough for a badge!

    The project documentation MUST publicly publish data about discovered vulnerabilities. [OSPS-VM-04.01]
    Provide information about known vulnerabilities in a predictable public channel, such as a CVE entry, blog post, or other medium. To the degree possible, this information should include affected version(s), how a consumer can determine if they are vulnerable, and instructions for mitigation or remediation.

    Resolved vulnerabilities are published as GitHub Security Advisories on the repository's public security tab, and security-relevant fixes are described in the release notes as documented in SECURITY.md. See https://github.com/netresearch/timetracker/security/advisories



You can use tools and AI systems to propose changes via a simple URL, such as https://www.bestpractices.dev/en/projects/11719/choose/edit?osps_ac_01_01_status=Met&osps_ac_01_01_justification=GitHub+enforced. See our automation proposals system for how to do that. This data is available under the Community Data License Agreement – Permissive, Version 2.0 (CDLA-Permissive-2.0). This means that a Data Recipient may share the Data, with or without modifications, so long as the Data Recipient makes available the text of this agreement with the shared Data. Please credit Sebastian Mendel and the OpenSSF Best Practices badge contributors.

Project badge entry owned by: Sebastian Mendel.
Entry created on 2026-01-09 06:05:12 UTC, last updated on 2026-09-18 08:02:02 UTC. Last achieved passing badge on 2026-02-25 23:03:38 UTC.