Update ci.yml

[matiasozdy]

Removing GH secret

[matiasozdy]

badger all

[jenkins-tf]

Badges for kube-node-cloudwatch

• Current level: not applicable
• Description: assess if package.json includes the desired accessibility tools

---

• Current level: 1/1
• Description: assess the presence of the ci standard checks workflow

---

• Current level: 1/1
• Description: assess the ownership of a repository

---

• Current level: not applicable
• Description: Assess if a repository is up-to-date with the version of @Typeform dependencies

---

• Current level: not applicable
• Description: Evaluates the usage of the 499/599 error codes standard in a repository

---

• Current level: not applicable
• Description: assesses the usage of Event Dispatcher to publish events

---

• Current level: not applicable
• Description: assess the presence of a canary config file

---

• Current level: 1/1
• Description: Assess if the repository's Github Actions is using secrets as environment variables

---

• Current level: not applicable
• Description: assesses the usage of the common Go Lint workflow

---

• Current level: not applicable
• Description: assesses the usage of the Common Go Service Starter

---

• Current level: not applicable
• Description: Assess if a repository has the Incident Handling playbook file

---

• Current level: not applicable
• Description: assess the presence of the ci standard checks workflow

---

• Current level: not applicable
• Description: This Badge is not applicable to this repository because it is not written in Typescript or Javascript

---

• Current level: not applicable
• Description: assesses Typescript setup in a repository

---

• Current level: not applicable
• Description: assess if requirements.txt includes the desired ml-model-promoter package

---

• Current level: not applicable
• Description: assesses Required Typescript setup in a repository

---

• Current level: 4/4
• Description: Evaluate the presence of type and use topics in a repository

---

• Current level: not applicable
• Description: Evaluates the presence of Jira issue keys in the PRs of a repository

---

• Current level: 1/1
• Description: Evaluate the default_branch of a repository is main

---

• Current level: not applicable
• Description: Assesses if a service is adding the proper metadata section in its generated events

---

• Current level: not applicable
• Description: assesses the usage of Flagger for deployments

---

• Current level: 2/2
• Description: assess the repository's dependencies from a security point of view

---

• Current level: 0/2
• Description: assess the repository's container image from a security point of view

Level-up recommendations

You are in this level because the repo has a container image and is not added to Snyk.

Recommendations:

• Add the container image to your Snyk organization +More info
• The vulnerable container image has a fix available, a Snyk Priority Score of 700 or more, and it was identified by Snyk more than 20 days ago +More info

---

• Current level: 1/1
• Description: assesses that a repository visibility is internal

---

• Current level: 0/1
• Description: assess the repository's branch protection rules

Level-up recommendations

You are in this level because the repo has a non compliant branch protection rules.

Recommendations:

• Set up branch protection rules +More info

---

• Current level: not applicable
• Description: Assesses if a service has tracing enabled in Datadog

---

• Current level: not applicable
• Description: assesses if application uses IAM auth instead of a password

---

Do you have any feedback on the Badger app? Please fill out this typeform

[matiasozdy]

badger all

[jenkins-tf]

Badges for kube-node-cloudwatch

• Current level: not applicable
• Description: assess if package.json includes the desired accessibility tools

---

• Current level: 1/1
• Description: assess the presence of the ci standard checks workflow

---

• Current level: 1/1
• Description: assess the ownership of a repository

---

• Current level: not applicable
• Description: Assess if a repository is up-to-date with the version of @Typeform dependencies

---

• Current level: not applicable
• Description: Evaluates the usage of the 499/599 error codes standard in a repository

---

• Current level: not applicable
• Description: assesses the usage of Event Dispatcher to publish events

---

• Current level: not applicable
• Description: assess the presence of a canary config file

---

• Current level: 1/1
• Description: Assess if the repository's Github Actions is using secrets as environment variables

---

• Current level: not applicable
• Description: assesses the usage of the common Go Lint workflow

---

• Current level: not applicable
• Description: assesses the usage of the Common Go Service Starter

---

• Current level: not applicable
• Description: Assess if a repository has the Incident Handling playbook file

---

• Current level: not applicable
• Description: assess the presence of the ci standard checks workflow

---

• Current level: not applicable
• Description: This Badge is not applicable to this repository because it is not written in Typescript or Javascript

---

• Current level: not applicable
• Description: assesses Typescript setup in a repository

---

• Current level: not applicable
• Description: assess if requirements.txt includes the desired ml-model-promoter package

---

• Current level: not applicable
• Description: assesses Required Typescript setup in a repository

---

• Current level: 4/4
• Description: Evaluate the presence of type and use topics in a repository

---

• Current level: not applicable
• Description: Evaluates the presence of Jira issue keys in the PRs of a repository

---

• Current level: 1/1
• Description: Evaluate the default_branch of a repository is main

---

• Current level: not applicable
• Description: Assesses if a service is adding the proper metadata section in its generated events

---

• Current level: not applicable
• Description: assesses the usage of Flagger for deployments

---

• Current level: 2/2
• Description: assess the repository's dependencies from a security point of view

---

• Current level: 0/2
• Description: assess the repository's container image from a security point of view

Level-up recommendations

You are in this level because the repo has a container image and is not added to Snyk.

Recommendations:

• Add the container image to your Snyk organization +More info
• The vulnerable container image has a fix available, a Snyk Priority Score of 700 or more, and it was identified by Snyk more than 20 days ago +More info

---

• Current level: 1/1
• Description: assesses that a repository visibility is internal

---

• Current level: 0/1
• Description: assess the repository's branch protection rules

Level-up recommendations

You are in this level because the repo has a non compliant branch protection rules.

Recommendations:

• Set up branch protection rules +More info

---

• Current level: not applicable
• Description: Assesses if a service has tracing enabled in Datadog

---

• Current level: not applicable
• Description: assesses if application uses IAM auth instead of a password

---

Do you have any feedback on the Badger app? Please fill out this typeform