search

falcosecurity / evolution

Evolution process of The Falco Project
Apache License 2.0
47 stars 37 forks source link

Donating rohith-raju/Flaco-playground (GSoC 2023 project) to falco organization #303

Closed Rohith-Raju closed 10 months ago

Rohith-Raju commented 11 months ago

Project

Repo: https://github.com/rohith-raju/falco-playground Playground: https://rohith-raju.github.io/falco-playground/

I had the pleasure of working on a project for Google Summer of Code (GSoC) with my mentor, @jasondellaluce. It was a fantastic experience from start to finish, and I'm grateful to all the members who made this my best summer yet. Together, we've decided to donate our project, which we've named falcosecurity/playground, to the Falcosecurity organization. We plan to continue improving it, with @jasondellaluce, @leogr, and myself taking on the responsibility of maintaining falco-playground. If any Falco maintainers would like to volunteer as a maintainer for falco-playground, we would greatly appreciate it!

Motivation

The idea for this project is to add WebAssembly as a new officially-supported compilation target for Falco by leveraging the Emscripten toolchain, and creating a new development environment for security rules in the form of a web single-page application by running Falco right inside the browser. The end result is envisioned to be similar to the Go Playground, but without the need of any backend.

Current state

I am happy to report that the project has been successfully constructed using React and is functioning exceptionally well. As per the guidelines of the GSoC program, it is mandatory for the students to submit a functional MVP/prototype by the end of the program. If you are interested in knowing more about the proposal, you can refer to #262. For more info about the submission please click on the following link: https://developers.google.com/open-source/gsoc/help/work-product.

Updates / Improvements

During a recent Falco community meeting, I shared a demo and received many helpful suggestions. One such suggestion was to validate the rule file with multiple Falco versions. This feature will be supported by upcoming Falco versions, as Falco can now be compiled to wasm. We have also taken into account suggestions for code refactoring and adding more test cases. Additionally, we welcome any feature requests or bug reports from the community.

leogr commented 11 months ago

Ofc, big +1 from me :star_struck:

maxgio92 commented 11 months ago

Amazing @Rohith-Raju and @jasondellaluce!

+1

FedeDP commented 11 months ago

Big big +1 from me!

loresuso commented 11 months ago

Great job, +1!

zuc commented 11 months ago

Amazing! +1 from me

Andreagit97 commented 11 months ago

amazing work! +1

jasondellaluce commented 11 months ago

It's been a pleasure to support you in your GSoC project, and I'm truly proud of how everything turned out becoming reality.

+1, looking forward to seeing this becoming part of our community's tool arsenal!

mikegcoleman commented 11 months ago

This is super cool. Congrats!

leogr commented 11 months ago

cc @falcosecurity/core-maintainers

incertum commented 11 months ago

Big +1 amazing work!

leogr commented 10 months ago

This is done! /close

poiana commented 10 months ago

@leogr: Closing this issue.

In response to [this](https://github.com/falcosecurity/evolution/issues/303#issuecomment-1711703070): >This is done! >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.