unguard icon indicating copy to clipboard operation
unguard copied to clipboard

Unguard is an insecure cloud-native microservices demo application.

Results 11 unguard issues
Sort by recently updated
recently updated
newest added

The more complex the services get, the better we should ensure that all the individual components start up and run correctly. If we implement liveness, readiness, and startup probes, Kubernetes...

enhancement

The docs in `docs/TRACING.md` refer to hardcoded versions of the `jaeger-operator` helm chart that is incompatible with more recent K8s versions. We should cut everything from that documentation page that...

enhancement
good first issue

**Is your feature request related to a problem? Please describe.** I believe we can easily reduce the complexity of the quickstart guide by making MariaDB a dependency that is automatically...

enhancement

Currently "unguard" is hard coded in many parts of the helm chart. Use the helm release-name instead. The helm release name can be referenced in the chart using the function...

enhancement

Could the adservice include some malicious third party ads that hog CPU and thus simulate crypto mining attacks?

enhancement

We would like to have playgrounds for Unguard so that users can easily test out the different functionality and see how the microservices work together (similar to the [HipsterShop](https://github.com/GoogleCloudPlatform/microservices-demo) "Open...

enhancement

We're considering adding [pre-commit](https://pre-commit.com/) to our project to help ensure that the code we commit to our repository is high quality. Pre-commit is a tool that allows us to define...

enhancement
good first issue

Right now, the name of the JVM is hardcoded in the [Gradle file](https://github.com/dynatrace-oss/unguard/blob/master/.idea/gradle.xml#L11), which is a problem if your JVM in IntelliJ has a different name. Additionally, changes to the...

enhancement
good first issue

We're using SonarQube to scan our codebase for potential issues and vulnerabilities. However, we have noticed several issues flagged by SonarQube that we need to address.

good first issue

The image sizes that we deploy are too big. With a local cluster, loading them into the cluster already takes minutes. Can this be reduced? Do we possibly include artifacts...

enhancement