HiveDAV

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:

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/14270/baseline)](https://www.bestpractices.dev/projects/14270)

or by embedding this in your HTML:

<a href="https://www.bestpractices.dev/projects/14270"><img src="https://www.bestpractices.dev/projects/14270/baseline"></a>

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

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

Basics

General

What is the human-readable name of the project?
Note that other projects may use the same name.

What is a brief description of the project?

A curlable free/busy scheduler with CalDAV integration.

What is the URL for the project (as a whole)?
https://hivedav.p0c.ch

What is the URL for the version control repository (it may be the same as the project URL)?
https://code.in0rdr.ch/hivedav

What license(s) is the project released under?
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.

What programming language(s) are used to implement the project?
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".

What is the Common Platform Enumeration (CPE) name for the project (if it has one)?
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.

Other general comments about the project:

A development instance and reference scheduler is hosted on https://meet.in0rdr.ch, try "curl meet.in0rdr.ch".

Controls 24/24 ●

Controls

Criterion [OSPS-AC-01.01]
Met

Unmet

N/A

?

When a user attempts to read or modify a sensitive resource in the project's authoritative repository, the system MUST require the user to complete a multi-factor authentication process. ^{[OSPS-AC-01.01]}
Enforce multi-factor authentication for the project's version control system, requiring collaborators to provide a second form of authentication when accessing sensitive data or modifying repository settings. Passkeys are acceptable for this control.

The Git repository allows pull-requests with picosh (https://pr.in0rdr.ch/repos/hivedav). No authentication required (except the identification with SSH pubkey, to attribute the patches to the user).

It's a "pastebin for patches" (from the community), which are then applied by the maintainer(s) using SSH credentials. There is no MFA on the SSH keys registered with the Git server (https://git.in0rdr.ch/hivedav.git), which is simply "Git on the server".

The "Stagit Web Interface" (https://code.in0rdr.ch/nomad/file/hcl/default/git/README.md.html) does not allow to do changes, it's a read-only & public interface.
Criterion [OSPS-AC-02.01]
Met

Unmet

N/A

?

When a new collaborator is added, the version control system MUST require manual permission assignment, or restrict the collaborator permissions to the lowest available privileges by default. ^{[OSPS-AC-02.01]}
Most public version control systems are configured in this manner. Ensure the project's version control system always assigns the lowest available permissions to collaborators by default when added, granting additional permissions only when necessary.
Git push permissions on the repository are constrained by htpasswd (Smart HTTP, see https://git-scm.com/book/en/v2/Git-on-the-Server-Smart-HTTP).
- https://code.in0rdr.ch/nomad/file/hcl/default/git/README.md.html
Collaborators can contribute patch sets through https://pr.in0rdr.ch/repos/hivedav.

Collaborators on pr.in0rdr.ch are not added specifically. Any user with SSH public key is allowed to contribute code (patches).
Criterion [OSPS-AC-03.01]
Met

Unmet

N/A

?

When a direct commit is attempted on the project's primary branch, an enforcement mechanism MUST prevent the change from being applied. ^{[OSPS-AC-03.01]}
If the VCS is centralized, set branch protection on the primary branch in the project's VCS. Alternatively, use a decentralized approach, like the Linux kernel's, where changes are first proposed in another repository, and merging changes into the primary repository requires a specific separate act.
Direct commits happen frequently on the master branch. This branch is the development branch.

Patches from contributors (https://pr.in0rdr.ch/repos/hivedav) are merged into the master branch or patched in the master branch directly (w/o merge branch).

Tags on the master branch are used to reference stable releases:
- https://code.in0rdr.ch/hivedav/refs.html
Criterion [OSPS-AC-03.02]
Met

Unmet

N/A

?

When an attempt is made to delete the project's primary branch, the version control system MUST treat this as a sensitive activity and require explicit confirmation of intent. ^{[OSPS-AC-03.02]}
Set branch protection on the primary branch in the project's version control system to prevent deletion.

The action "delete Git branch" is protected by the SSH keys. Only maintainers with the appropriate SSH keys on the Git server can (https://git-scm.com/book/en/v2/Git-on-the-Server-Smart-HTTP) delete the "primary branch" (called "master" in our project).

Criterion [OSPS-BR-01.01]
Met

Unmet

N/A

?

When a CI/CD pipeline operates on untrusted metadata, those parameters MUST be sanitized and validated prior to use in the pipeline. ^{[OSPS-BR-01.01]}
CI/CD pipelines should sanitize (quote, escape or exit on expected values) all metadata inputs which correspond to untrusted sources. This includes data such as branch names, commit messages, tags, pull request titles, and author information.

The Jenkins pipeline uses the GIT_COMMIT metadata to create container builds with Buildah (https://code.in0rdr.ch/hivedav/file/Jenkinsfile.html).

We assume the Jenkins generic SCM step (https://plugins.jenkins.io/workflow-scm-step/#plugin-content-generic-scm-step) provides us with the sanitized metadata.

Criterion [OSPS-BR-01.03]
Met

Unmet

N/A

?

When a CI/CD pipeline operates on untrusted code snapshots, it MUST prevent access to privileged CI/CD credentials and assets. ^{[OSPS-BR-01.03]}
CI/CD pipelines should isolate untrusted code snapshots from privileged credentials and assets. In particular, projects should be careful to ensure that workflows which build or execute code prior to review by a collaborator do not have access to CI/CD credentials.

CICD credentials in Jenkins for fetching the latest code from Git are protected with OpenBao (https://code.in0rdr.ch/hivedav/file/Jenkinsfile.html).

See also https://plugins.jenkins.io/hashicorp-vault-plugin.

Criterion [OSPS-BR-03.01]
Met

Unmet

N/A

?

When the project lists a URI as an official project channel, that URI MUST be exclusively delivered using encrypted channels. ^{[OSPS-BR-03.01]}
Configure the project's websites and version control systems to use encrypted channels such as SSH or HTTPS for data transmission. Ensure all tools and domains referenced in project documentation can only be accessed via encrypted channels.

Project URLs use HTTPS exclusively.

Criterion [OSPS-BR-03.02]
Met

Unmet

N/A

?

When the project lists a URI as an official distribution channel, that channel MUST be protected from adversary-in-the-middle attacks using cryptographically authenticated channels. ^{[OSPS-BR-03.02]}
Artifacts distributed by the project should be distributed through channels which ensure integrity and authenticity. Use of HTTPS for downloads, signed releases, or distribution through trusted package managers are all acceptable methods to protect against adversary-in-the-middle attacks.

Distribution channels use HTTPS exclusively.
Criterion [OSPS-BR-07.01]
Met

Unmet

N/A

?

The project MUST prevent the unintentional storage of unencrypted sensitive data, such as secrets and credentials, in the version control system. ^{[OSPS-BR-07.01]}
Configure .gitignore or equivalent to exclude files that may contain sensitive information. Use pre-commit hooks and automated scanning tools to detect and prevent the inclusion of sensitive data in commits.
The project pipeline uses Trivy vulnerability scanning to detect any secrets or sensitive data in the Git repo.
The Trivy scanners used:
- vuln
- misconfig
- secret
- license
Criterion [OSPS-DO-01.01]
Met

Unmet

N/A

?

When the project has made a release, the project documentation MUST include user guides for all basic functionality. ^{[OSPS-DO-01.01]}
Create user guides or documentation for all basic functionality of the project, explaining how to install, configure, and use the project's features. If there are any known dangerous or destructive actions available, include highly-visible warnings.
The following Readme files and documentation are included with each release/tag:
- How to release: https://code.in0rdr.ch/hivedav/file/RELEASES.md.html
- How to setup & use: https://code.in0rdr.ch/hivedav/file/README.md.html
- Development/implementation details: https://code.in0rdr.ch/hivedav/file/docs/CALDAV.md.html
Additional files might be provided in the future, to further document the system as needed.
Criterion [OSPS-DO-02.01]
Met

Unmet

N/A

?

When the project has made a release, the project documentation MUST include a guide for reporting defects. ^{[OSPS-DO-02.01]}
It is recommended that projects use their VCS default issue tracker. If an external source is used, ensure that the project documentation and contributing guide clearly and visibly explain how to use the reporting system. It is recommended that project documentation also sets expectations for how defects will be triaged and resolved.
See bottom of the Readme:
- https://code.in0rdr.ch/hivedav/file/README.md.html#l218
Defects/issues can be reported via IRC and the web.libera.chat interface.

The issues are recorded and tracked in a public Kanboard:
- https://board.in0rdr.ch/public/board/01171363fae4b8b81af1579708f7cda6d389062f05b75db860621eaed32b
```
## Development & Contributions
* All source code is available in this repository. Contributions are always
  welcome! Pull requests at https://pr.in0rdr.ch/repos/hivedav
* A [Kanban
  board](https://board.in0rdr.ch/public/board/01171363fae4b8b81af1579708f7cda6d389062f05b75db860621eaed32b)
documents plans, todos and decisions for further development of the project.

## Community and Support
For question and support visit
[#p0c/libera](https://web.libera.chat/gamja/#p0c) on IRC.
```
Criterion [OSPS-GV-02.01]
Met

Unmet

N/A

?

The project MUST have one or more mechanisms for public discussions about proposed changes and usage obstacles. ^{[OSPS-GV-02.01]}
Establish one or more mechanisms for public discussions within the project, such as mailing lists, instant messaging, or issue trackers, to facilitate open communication and feedback.

See the README.

For question and support visit #p0c/libera (https://web.libera.chat/gamja/#p0c) on IRC.

Discussions via patch sets are encouraged as well (https://pr.in0rdr.ch/repos/hivedav)
Criterion [OSPS-GV-03.01]
Met

Unmet

N/A

?

The project documentation MUST include an explanation of the contribution process, or clearly state that public contributions are not accepted ^{[OSPS-GV-03.01]}
Create a CONTRIBUTING.md or CONTRIBUTING/ directory to outline the contribution process including the steps for submitting changes, and engaging with the project maintainers.
There is no "process" setup specifically for the contribution. The "process" is kept simple/lean.

See bottom of the Readme:
- https://code.in0rdr.ch/hivedav/file/README.md.html#l218
All source code is available in this repository. Contributions are always welcome! Pull requests at https://pr.in0rdr.ch/repos/hivedav
Criterion [OSPS-LE-02.01]
Met

Unmet

N/A

?

The license for the source code MUST meet the OSI Open Source Definition or the FSF Free Software Definition. ^{[OSPS-LE-02.01]}
Add a LICENSE file to the project's repo with a license that is an approved license by the Open Source Initiative (OSI), or a free license as approved by the Free Software Foundation (FSF). Examples of such licenses include the MIT, BSD 2-clause, BSD 3-clause revised, Apache 2.0, Lesser GNU General Public License (LGPL), and the GNU General Public License (GPL). Releasing to the public domain meets this control if there are no other encumbrances such as patents.

The MIT license for the repository contents is approved by the Open Source Initiative (OSI).

Criterion [OSPS-LE-02.02]
Met

Unmet

N/A

?

The license for the released software assets MUST meet the OSI Open Source Definition or the FSF Free Software Definition. ^{[OSPS-LE-02.02]}
If a different license is included with released software assets, ensure it is an approved license by the Open Source Initiative (OSI), or a free license as approved by the Free Software Foundation (FSF). Examples of such licenses include the MIT, BSD 2-clause, BSD 3-clause revised, Apache 2.0, Lesser GNU General Public License (LGPL), and the GNU General Public License (GPL). Note that the license for the released software assets may be different than the source code.

The MIT license is approved by the Open Source Initiative (OSI). [floss_license]

Criterion [OSPS-LE-03.01]
Met

Unmet

N/A

?

The license for the source code MUST be maintained in the corresponding repository's LICENSE file, COPYING file, LICENSES/ directory, or LICENSE/ directory. ^{[OSPS-LE-03.01]}
Include the project's source code license in the project's LICENSE file, COPYING file, LICENSES/ directory, or LICENSE/ directory to provide visibility and clarity on the licensing terms. The filename MAY have an extension. If the project has multiple repositories, ensure that each repository includes the license file.

see https://code.in0rdr.ch/hivedav/file/LICENSE.html
Criterion [OSPS-LE-03.02]
Met

Unmet

N/A

?

The license for the released software assets MUST be included in the released source code, or in a LICENSE file, COPYING file, or LICENSE/ directory alongside the corresponding release assets. ^{[OSPS-LE-03.02]}
Include the project's released software assets license in the released source code, or in a LICENSE file, COPYING file, or LICENSE/ directory alongside the corresponding release assets to provide visibility and clarity on the licensing terms. The filename MAY have an extension. If the project has multiple repositories, ensure that each repository includes the license file.
The LICENSE file is included in the releases/tags:
- https://code.in0rdr.ch/hivedav/file/LICENSE.html
Criterion [OSPS-QA-01.01]
Met

Unmet

N/A

?

The project's source code repository MUST be publicly readable at a static URL. ^{[OSPS-QA-01.01]}
Use a common VCS such as GitHub, GitLab, or Bitbucket. Ensure the repository is publicly readable. Avoid duplication or mirroring of repositories unless highly visible documentation clarifies the primary source. Avoid frequent changes to the repository that would impact the repository URL. Ensure the repository is public.

see https://code.in0rdr.ch/hivedav

Criterion [OSPS-QA-01.02]
Met

Unmet

N/A

?

The version control system MUST contain a publicly readable record of all changes made, who made the changes, and when the changes were made. ^{[OSPS-QA-01.02]}
Use a common VCS such as GitHub, GitLab, or Bitbucket to maintain a publicly readable commit history. Avoid squashing or rewriting commits in a way that would obscure the author of any commits.

see https://code.in0rdr.ch/hivedav/log.html

Criterion [OSPS-QA-02.01]
Met

Unmet

N/A

?

When the package management system supports it, the source code repository MUST contain a dependency list that accounts for the direct language dependencies. ^{[OSPS-QA-02.01]}
This may take the form of a package manager or language dependency file that enumerates all direct dependencies such as package.json, Gemfile, or go.mod.

see https://code.in0rdr.ch/hivedav/file/go.mod.html

Criterion [OSPS-QA-04.01]
Met

Unmet

N/A

?

Projects with multiple repositories MUST document a list of codebases that are part of the project. ^{[OSPS-QA-04.01]}
Document any additional subproject code repositories produced by the project and compiled into a release. This documentation should include the status and intent of the respective codebase.

The mentioned Git repo is the single source of truth for the project.

Criterion [OSPS-QA-05.01]
Met

Unmet

N/A

?

The version control system MUST NOT contain generated executable artifacts. ^{[OSPS-QA-05.01]}
Remove generated executable artifacts in the project's version control system. It is recommended that any scenario where a generated executable artifact appears critical to a process such as testing, it should be instead be generated at build time or stored separately and fetched during a specific well-documented pipeline step.

Criterion [OSPS-QA-05.02]
Met

Unmet

N/A

?

The version control system MUST NOT contain unreviewable binary artifacts. ^{[OSPS-QA-05.02]}
Do not add any unreviewable binary artifacts to the project's version control system. This includes executable application binaries, library files, and similar artifacts. It does not include assets such as graphical images, sound or music files, and similar content typically stored in a binary format.
Criterion [OSPS-VM-02.01]
Met

Unmet

N/A

?

The project documentation MUST contain security contacts. ^{[OSPS-VM-02.01]}
Create a security.md (or similarly-named) file that contains security contacts for the project.
We use the IRC chat as single point of contact.

For the SECURITY readme file, see:
- https://board.in0rdr.ch/public/task/72/01171363fae4b8b81af1579708f7cda6d389062f05b75db860621eaed32b

You can use tools and AI systems to propose changes via a simple URL, such as https://www.bestpractices.dev/en/projects/14270/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 Andreas Gruhler and the OpenSSF Best Practices badge contributors.

HiveDAV

Basics

General

Controls 24/24 ●

Controls