Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status

The cis-el7-l1-hardening cookbook has been deprecated

Author provided reason for deprecation:

The cis-el7-l1-hardening cookbook has been deprecated and is no longer being maintained by its authors. Use of the cis-el7-l1-hardening cookbook is no longer recommended.


cis-el7-l1-hardening (2) Versions 0.6.2

Installs/Configures cis-el7-l1-hardening

cookbook 'cis-el7-l1-hardening', '= 0.6.2', :supermarket
cookbook 'cis-el7-l1-hardening', '= 0.6.2'
knife supermarket install cis-el7-l1-hardening
knife supermarket download cis-el7-l1-hardening
Quality 57%


This cookbook provides recipes for ensuring that a RHEL-7 system is compliant with the Lightweight CIS-L1 Chef Compliance profile.

Coding guidelines

Use Chef resources wherever possible. The line cookbook is included for making line by line substitutions in config files. See the enable_sudo_no_tty.rb for
a usage example.

Testing the cookbook

As the results of the cookbook need to be verified by running a Compliance scan against them it is recommended to use an EC2 test-kitchen instance. The default .kitchen.yml file creates one using the emea-sa-shared key.

Adding your test-kitchen instance to Compliance automatically

The provided Rakefile has two tasks to allow you to automatically add your test-kitchen instance into Compliance:

rake setup_compliance_creds

This asks for your Compliance Server username and your Compliance Refresh token as input and creates a .compliance-creds file in the root of the cookbook. You can obtain your refresh token from the Compliance UI when logged in by clicking the user icon in the top right of the screen and clicking about

Note that the refresh token is long lived so you don't need to regenerate your compliance-creds unless .compliance-creds gets deleted

rake add_compliance_node

Automatically adds the test-kitchen node to Compliance with the correct user credentials.

Note that this assumes you already have a private key setup in Compliance called emea-sa-shared

Dependent cookbooks

line ~> 0.6.3

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric

0.6.2 passed this metric

Contributing File Metric

0.6.2 passed this metric

Foodcritic Metric

0.6.2 failed this metric

FC008: Generated cookbook metadata needs updating: cis-el7-l1-hardening/metadata.rb:2
FC066: Ensure chef_version is set in metadata: cis-el7-l1-hardening/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: cis-el7-l1-hardening/metadata.rb:1
FC069: Ensure standardized license defined in metadata: cis-el7-l1-hardening/metadata.rb:1
Run with Foodcritic Version 12.0.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric

0.6.2 failed this metric

cis-el7-l1-hardening does not have a valid open source license.
Acceptable licenses include Apache-2.0, apachev2, Apache 2.0, MIT, mit, GPL-2.0, gplv2, GNU Public License 2.0, GPL-3.0, gplv3, GNU Public License 3.0.

No Binaries Metric

0.6.2 passed this metric

Testing File Metric

0.6.2 passed this metric

Version Tag Metric

0.6.2 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of, and your repo must include a tag that matches this cookbook version number