cwielenb/CNCF-Dataset huggingface dataset:
Project: Polaris (Provisioning / Security & Compliance)
File: code-of-conduct.md

meta: name: description content: "Fairwinds Polaris | Contribution Code of Conduct" In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. Examples of behavior that contributes to creating a positive environment include: Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include: The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [INSERT EMAIL ADDRESS]. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. This Code of Conduct is adapted from the , version 1.4, available at
Project: FOSSA (Provisioning / Security & Compliance)
File: stack.md

Find all directories with a `stack.yaml` file. When one is found, skip all subdirectories. From the project root, we run `stack ls dependencies json`, which outputs JSON in the following format. Extra data removed for brevity ``` json [ { "location": { "type": "hackage" }, "name": "remote", "version": "remote-ver", "dependencies": [ "deep" ] }, { "location": { "type": "project package" }, "name": "local", "version": "local-ver", "dependencies": [ "remote", "builtin" ] }, { "location": { "type": "hackage" }, "name": "deep", "version": "deep-ver", "dependencies": [] }, { "name": "builtin", "version": "builtin-ver" } ] ``` Analysis has two notable parts: matching `name` fields from the strings in `dependencies`, and noting the package's `location.type`. A package with a missing `location.type` refers to a builtin, ghc-provided package, and a present field takes one of two forms: remote and local, which have different sets of string associated with them. Local packages are references to the current project, while remote references are pointers to package or source repositories.
Project: KICS (Provisioning / Security & Compliance)
File: c87749b3-ff10-41f5-9df2-c421e8151759.md

title: Function App Managed Identity Disabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: c87749b3-ff10-41f5-9df2-c421e8151759 Query name: Function App Managed Identity Disabled Platform: Terraform Severity: <span style="color:#ff7213">Medium</span> Category: Insecure Configurations URL: Azure Function App should have managed identity enabled<br> ```tf title="Positive test num. 1 - tf file" hl_lines="1" resource "azurermfunctionapp" "positive1" { name = "test-azure-functions" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id storageaccountname = azurermstorageaccount.example.name storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key } ``` ```tf title="Negative test num. 1 - tf file" resource "azurermfunctionapp" "negative" { name = "test-azure-functions" location = azurermresourcegroup.example.location resourcegroupname = azurermresourcegroup.example.name appserviceplanid = azurermappserviceplan.example.id storageaccountname = azurermstorageaccount.example.name storageaccountaccesskey = azurermstorageaccount.example.primaryaccess_key identity { type = "SystemAssigned" } } ```
Project: KICS (Provisioning / Security & Compliance)
File: f81d63d2-c5d7-43a4-a5b5-66717a41c895.md

title: ALB Listening on HTTP hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: f81d63d2-c5d7-43a4-a5b5-66717a41c895 Query name: ALB Listening on HTTP Platform: Ansible Severity: <span style="color:#ff7213">Medium</span> Category: Networking and Firewall URL: AWS Application Load Balancer (alb) should not listen on HTTP<br> ```yaml title="Positive test num. 1 - yaml file" hl_lines="11 29" name: myelbapplication community.aws.elbapplicationlb: name: myelb security_groups: sg-12345678 my-sec-group subnets: subnet-012345678 subnet-abcdef000 listeners: Protocol: HTTP Port: 80 SslPolicy: ELBSecurityPolicy-2015-05 Certificates: CertificateArn: arn:aws:iam::12345678987:server-certificate/test.domain.com DefaultActions: Type: forward TargetGroupName: targetname state: present name: myelbapplication2 community.aws.elbapplicationlb: name: myelb2 security_groups: sg-12345678 my-sec-group subnets: subnet-012345678 subnet-abcdef000 listeners: Port: 80 SslPolicy: ELBSecurityPolicy-2015-05 Certificates: CertificateArn: arn:aws:iam::12345678987:server-certificate/test.domain.com DefaultActions: Type: forward TargetGroupName: targetname state: present ``` ```yaml title="Negative test num. 1 - yaml file" name: myelbapplication community.aws.elbapplicationlb: name: myelb security_groups: sg-12345678 my-sec-group subnets: subnet-012345678 subnet-abcdef000 listeners: Protocol: HTTPS Port: 80 SslPolicy: ELBSecurityPolicy-2015-05 Certificates: CertificateArn: arn:aws:iam::12345678987:server-certificate/test.domain.com DefaultActions: Type: forward TargetGroupName: targetname state: present ```
Project: Meshery (Provisioning / Automation & Configuration)
File: v0.6.95.md

layout: release date: 2023-06-15 tag: v0.6.95 [performance] add support for labels @MUzairS15 (#7870) policies: Fix the detection of the relationship in existing policy @Abhishek-kumar09 (#7864) [Mesheryctl] Support tailing logs in Kubernetes platform @Meyazhagan (#7801) Change adapter API callback argument for mesheryctl check @alphaX86 (#7862) [Catalog] make all the fields required in the RJSF form while submitting the catalog request @Abhishek-kumar09 (#7868) [UI] - disable deploy and undeploy @UsmanDev09 (#7858) Bump github.com/jarcoal/httpmock from 1.2.0 to 1.3.0 @dependabot (#7776) [CI] Only release when called by stable release workflow @leecalcote (#7855) updated architecture page @thisiskaransgit (#7842) Thank you to our contributors for making this release possible: @Abhishek-kumar09, @MUzairS15, @Meyazhagan, @Revolyssup, @UsmanDev09, @alphaX86, @dependabot, @leecalcote, @thisiskaransgit and MUzairS15
Project: DevSpace (App Definition and Development / Application Definition & Image Build)
File: devspace_run.md

title: "Command - devspace run" sidebar_label: devspace run Run executes a predefined command ``` devspace run [flags] ``` ``` Run executes a predefined command from the devspace.yaml Examples: devspace run mycommand --myarg 123 devspace run mycommand2 1 2 3 devspace --dependency my-dependency run any-command --any-command-flag ``` ``` --dependency string Run a command from a specific dependency -h, --help help for run ``` ``` --config string The devspace config file to use --debug Prints the stack trace if an error occurs --disable-profile-activation If true will ignore all profile activations --inactivity-timeout int Minutes the current user is inactive (no mouse or keyboard interaction) until DevSpace will exit automatically. 0 to disable. Only supported on windows and mac operating systems (default 180) --kube-context string The kubernetes context to use -n, --namespace string The kubernetes namespace to use --no-warn If true does not show any warning when deploying into a different namespace or kube-context than before -p, --profile strings The DevSpace profiles to apply. Multiple profiles are applied in the order they are specified --profile-parent strings One or more profiles that should be applied before the specified profile (e.g. devspace dev --profile-parent=base1 --profile-parent=base2 --profile=my-profile) --profile-refresh If true will pull and re-download profile parent sources --restore-vars If true will restore the variables from kubernetes before loading the config --save-vars If true will save the variables to kubernetes after loading the config --silent Run in silent mode and prevents any devspace log output except panics & fatals -s, --switch-context DEPRECATED: Switches and uses the last kube context and namespace that was used to deploy the DevSpace project --var strings Variables to override during execution (e.g. --var=MYVAR=MYVALUE) --vars-secret string The secret to restore/save the variables from/to, if --restore-vars or --save-vars is enabled (default "devspace-vars") ```
Project: FOSSA (Provisioning / Security & Compliance)
File: yarn.md

Yarn is a spiritual successor to the npm cli. Yarn automatically updates the `yarn.lock` file when the yarn CLI is used to modify the dependencies present in the project. The `yarn.lock` file contains information about a dependency's transitive dependencies, its location, and its resolved version. Find all files named `yarn.lock` which have a corresponding `package.json` file. yarn.lock has its own bespoke format. Dependencies typically look something like: ```yarn-lock "@babel/code-frame@^7.0.0", "@babel/code-frame@^7.5.5": version "7.5.5" resolved "https://registry.yarnpkg.com/@babel/code-frame/-/code-frame-7.5.5.tgz#bc0782f6d69f7b7d49531219699b988f669a8f9d" integrity sha512-27d4lZoomVyo51VegxI20xZPuSHusqbQag/ztrBC7wegWoQ1nLREPVSKSW8byhTlzTKyNE4ifaTA6lCp7JjpFw== dependencies: "@babel/highlight" "^7.0.0" ``` where: `resolved` is the exact location of the dependency `version` is a pinned dependency the section "keys" contain constraints used by other packages to refer to this dependency `dependencies` is a list of constraints for dependencies of this package We also support yarn V2, which uses a similar, though mechanically different schema, but uses standard YAML rather than a bespoke format. As of v2.19.x, we also support yarn workspaces. In practice, this means that the `package.json` files used to build the `yarn.lock` file are also checked, and the knowledge of both is combined to form a (usually) complete picture of the full graph of dependencies. There are many default that Yarn allows users to fetch dependencies. The FOSSA CLI currently supports the `npm` and `git` protocols. <!-- We also support a tar protocol resolver, but this must be related to npm or a custom protocol because I can't find an example. -->
Project: StarRocks (App Definition and Development / Database)
File: hour.md

displayed_sidebar: "English" Returns the hour for a given date. The return value ranges from 0 to 23. The `date` parameter must be of the DATE or DATETIME type. ```Haskell INT HOUR(DATETIME|DATE date) ``` ```Plain Text MySQL > select hour('2018-12-31 23:59:59'); +--+ | hour('2018-12-31 23:59:59') | +--+ | 23 | +--+ ``` HOUR
Project: KICS (Provisioning / Security & Compliance)
File: 42bb6b7f-6d54-4428-b707-666f669d94fb.md

title: S3 Static Website Host Enabled hide: toc: true navigation: true <style> .highlight .hll { background-color: #ff171742; } .md-content { max-width: 1100px; margin: 0 auto; } </style> Query id: 42bb6b7f-6d54-4428-b707-666f669d94fb Query name: S3 Static Website Host Enabled Platform: Terraform Severity: <span style="color:#bb2124">High</span> Category: Insecure Configurations URL: Checks if any static websites are hosted on buckets. Even static websites can be a liability when poorly configured.<br> ```tf title="Positive test num. 1 - tf file" hl_lines="18" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 3.0" } } } resource "awss3bucket" "positive1" { bucket = "s3-website-test.hashicorp.com" acl = "public-read" website { index_document = "index.html" error_document = "error.html" } } ``` ```tf title="Positive test num. 2 - tf file" hl_lines="12" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } website { index_document = "index.html" error_document = "error.html" } } ``` ```tf title="Positive test num. 3 - tf file" hl_lines="15" terraform { required_providers { aws = { source = "hashicorp/aws" version = "4.2.0" } } } provider "aws" { } resource "awss3bucket" "buc" { bucket = "my-tf-test-bucket" tags = { Name = "My bucket" Environment = "Dev" } } resource "awss3bucketwebsiteconfiguration" "example" { bucket = awss3bucket.buc.bucket index_document { suffix = "index.html" } error_document { key = "error.html" } routing_rule { condition { keyprefixequals = "docs/" } redirect { replacekeyprefix_with = "documents/" } } } ``` ```tf title="Negative test num. 1 - tf file" provider "aws" { region = "us-east-1" } terraform { required_providers { aws = { source = "hashicorp/aws" version = "~> 3.0" } } } resource "awss3bucket" "negative1" { bucket = "s3-website-test.hashicorp.com" acl = "public-read" } ``` ```tf title="Negative test num. 2 - tf file" module "s3_bucket" { source = "terraform-aws-modules/s3-bucket/aws" version = "3.7.0" bucket = "my-s3-bucket" acl = "private" versioning = { enabled = true } } ``` ```tf title="Negative test num. 3 - tf file" terraform { required_providers { aws = { source = "hashicorp/aws" version = "4.2.0" } } } provider "aws" { } resource "awss3bucket" "bu" { bucket = "my-tf-test-bucket" tags = { Name = "My bucket" Environment = "Dev" } } ```
Project: Beam (App Definition and Development / Streaming & Messaging)
File: 27_io_parquet.md

Prompt: Is Apache Parquet format supported in Apache Beam? Response: is a data format for storing and exchanging data. Apache Beam supports reading from and writing to Parquet files using the `ReadFromParquet` and `WriteToParquet` transforms in the `ParquetIO` module. For more information, see the ParquetIO connector documentation for the following languages: To get started with Avro and Apache Beam, refer to the . Here is an example of Apache Beam pipeline code for reading data from a Parquet file: ```python class ReadParquetOptions(PipelineOptions): @classmethod def addargparse_args(cls, parser): parser.add_argument( "--path", help="GCS path to parquet file") options = ReadParquetOptions() with beam.Pipeline(options=options) as p: (p | "ReadParquet" >> ReadFromParquet(options.path) | Map(logging.info)) ```
Project: Dapr (App Definition and Development / Application Definition & Image Build)
File: v1.9.1.md

Users running Dapr in self-hosted mode and relying on the mDNS name resolver (the default when not running in Kubernetes) would encounter errors trying to perform service invocation if the system had IPv6 disabled. This issue impacts users who are: running Dapr in self-hosted mode, and using the default mDNS name resolver, and have disabled IPv6 on the operating system When initializing a zeroconf (mDNS) client, Dapr required using both IPv4 and IPv6, and failed if either one of the two protocols was disabled on the host system. We have improved error handling so Dapr gracefully falls back to using IPv4 if binding to IPv6 fails.
Project: Dgraph (App Definition and Development / Database)
File: template.md

```yaml RFC: PREFIX + NUMBER # Choose a unique number for your RFC. Title: RFC TITLE Author: NAME <EMAIL> # It can be Discuss user or any public email Co-Author: NAME <EMAIL> # It can be Discuss user or any public email and you can add more lines with co-authors. Status: STATUS # e.g., "Accepted," "Rejected" Type: TYPE # e.g., "Design," "Process," "Informational") Model: Model # e.g., "RFC," "Deprecation," "Post-mortem") Created: DATE # Not necessarily the day of publication Replaces: RFC NUMBER # Rejected, depreacted RFC or other. Superseded-By: NUMBER # It can be left blank if the RFC has not been superseded. ``` A brief summary of the RFC. Provide a brief overview of the main topics covered in the document. An explanation of the need for the RFC and the problem it aims to solve. If necessary, a high-level description of the design of the solution proposed in the RFC. This section may include pseudocode to clarify concepts. A detailed explanation of the technical implementation of the solution proposed in the RFC. An examination of the limitations and potential negative consequences of the solution proposed in the RFC. Such as impact in third parties tools, impact in the core, backwards Compatibility and so on. An exploration of other potential solutions to the problem addressed by the RFC. A plan for how the proposed solution in the RFC will be adopted and integrated into the Dgraph Core. -- Explanation(Delete this in your RFC): The "Type" field in an RFC template is used to categorize the type of proposal that the RFC represents. In the context of Dgraph, it can be used to indicate the nature or purpose of the proposal. Here are some examples of types that might be used in an RFC for Dgraph: Design: This type is used when the RFC proposes a new design or architecture for a feature or system in Dgraph products. Process: This type is used when the RFC proposes a new process or workflow for the development of Dgraph products. Informational: This type is used when the RFC provides information that is important to the development of Dgraph, but does not propose any changes to the design or process.
Project: Curiefense (Provisioning / Security & Compliance)
File: RELEASES.md

This release process is heavily inspired by release process. We have made a few changes to adapt to the size of our community, and the current state of the project. Active development is happening on the `main` branch, and a new version is released from it at the end of each quarter. Stable releases of Curiefense include: Security fixes backported from the `main` branch (including those deemed not worthy of creating a CVE). Stability fixes backported from the `main` branch (anything that can result in a crash, including crashes triggered by a trusted control plane). Bugfixes, deemed worthwhile by the maintainers of stable releases. Hand-off to the maintainers of stable releases happens after Curiefense maintainers release a new version from the `main` branch by creating a `vX.Y.0` tag and a corresponding `release/vX.Y` branch, with merge permissions given to the release manager of stable releases, and CI configured to execute tests on it. Critical security fixes are owned by the Curiefense security team, which provides fixes for the `main` branch, and the latest release branch. Once those fixes are ready, the maintainers of stable releases backport them to the remaining supported stable releases. All other security and reliability fixes can be nominated for backporting to stable releases by Curiefense maintainers, Curiefense security team, the change author, or members of the Curiefense community by adding the `backport/review` or `backport/approved` label. Changes nominated by the change author and/or members of the Curiefense community are evaluated for backporting on a case-by-case basis, and require approval from either the release manager of stable release, Curiefense maintainers, or Curiefense security team. Once approved, those fixes are backported from the `main` branch to all supported stable branches by the maintainers of stable releases. New stable versions from non-critical security fixes are released on a regular schedule, initially aiming for the bi-weekly releases. Release managers of stable releases are responsible for approving and merging backports, tagging stable releases and sending announcements about them. | Quarter | Release manager | |:-:|:--:| | 2021 Q1 | Justin Dorfman () | | 2021 Q2 | Justin Dorfman () | | 2021 Q3 | Justin Dorfman () | In order to accommodate downstream projects, new Curiefense releases are produced on a fixed release schedule (at the end of each quarter), with an acceptable delay of up to 2 weeks, with a hard deadline of 3 weeks. TBD: To Be Defined NRY: Not Released Yet | Version | Expected | Actual | Difference | End of Life | |:-:|:-:|:-:|:-:|:--:| | | 2021/03/02 | 2021/03/02 | +0 days | TBD | | | 2021/06/30 | 2021/07/27 | +27 days | TBD | | | 2021/08/31 | NRY | NRY | TBD |
Project: kube-hunter (Provisioning / Security & Compliance)
File: PULL_REQUEST_TEMPLATE.md

<! Thank you for contributing to Aqua Security. Please don't remove the template. --> Please include a summary of the change and which issue is fixed. Also include relevant motivation and context. List any dependencies that are required for this change. Please Read through the . Please mention any issues fixed in the PR by referencing it properly in the commit message. As per the convention, use appropriate keywords such as `fixes`, `closes`, `resolves` to automatically refer the issue. Please consult for details. Fixes #(issue) To verify that the change works as desired, please include an output of terminal before and after the changes under headings "BEFORE" and "AFTER". Any Terminal Output Before Changes. Any Terminal Output Before Changes. [ ] I have read the Contributing Guidelines. [ ] The commits refer to an active issue in the repository. [ ] I have added automated testing to cover this case. Please mention if you have not checked any of the above boxes.