ClojureDart
slsa
Our great sponsors
ClojureDart | slsa | |
---|---|---|
27 | 35 | |
1,334 | 1,422 | |
2.5% | 3.0% | |
9.2 | 8.7 | |
8 days ago | 4 days ago | |
Clojure | Shell | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ClojureDart
- ClojureDart – Clojure Dialect for Flutter and Dart
- Embedding Clojure into iOS Applications
-
Why Lisp?
> "ClojureDart is production-ready: you can ship applications right now.
Source: https://github.com/Tensegritics/ClojureDart
See a live demo here: https://www.youtube.com/watch?v=dqBeGpuedf0
ClojureDart is very similar to ClojureScript, which the GP is already comfortable with.
-
Is Clojure the only language you need?
Ah, and there is also a new version of Clojure in active development - ClojureDart. It is a port of Clojure language to Dart with the primary goal of using Flutter framework and getting a native mobile and desktop UI.
-
So you're using a weird language
There is a port of the Clojure language to Dart with Flutter support: https://github.com/Tensegritics/ClojureDart
-
What features should a Lisp IDE have?
Now https://github.com/Tensegritics/ClojureDart exist to build GUI with flutter.
-
language bindings?
There are ways, but it is generally a lot of work, for example there is ClojureDart https://github.com/Tensegritics/ClojureDart . Though unusually that sort of thing is normal for Clojure, because it is a hosted language (Clojure -> JVM, ClojureScript -> JS, etc).
- Jumping back in!
-
Clojure Single Codebase?
Something to checkout for mobile and desktop is: https://github.com/Tensegritics/ClojureDart
-
Clojure Scripting on Node.js
Basically, you take a programming language and make it work on a platform that meant to be programmed using a different PL. Clojure is hosted by design - it's not Java, but can be used to program for JVM. It ain't Javascript, but can be used to target nodejs and browser; not an [official] CLR language, but you can write .Net programs. You can use Clojure to make Flutter apps with ClojureDart. You can integrate Python into Clojure with libpython-clj. Or write Clojure to target Erlang/OTP; or Rust; or R; There's even a clojure-like language for Lua - Fennel.
There's something about Clojure people like so much, they want it to work atop any platform.
https://github.com/Tensegritics/ClojureDart
https://github.com/clj-python/libpython-clj
https://github.com/clojerl/clojerl
https://github.com/clojure-rs/ClojureRS
https://github.com/scicloj/clojisr
https://fennel-lang.org
slsa
- SLSA – Supply-Chain Levels for Software Artifacts
-
Dogbolt Decompiler Explorer
Short answer: not where it counts.
My work focuses on recognizing known functions in obfuscated binaries, but there are some papers you might want to check out related to deobfuscation, if not necessarily using ML for deobfuscation or decompilation.
My take is that ML can soundly defeat the "easy" and more static obfuscation types (encodings, control flow flattening, splitting functions). It's low hanging fruit, and it's what I worked on most, but adoption is slow. On the other hand, "hard" obfuscations like virtualized functions or programs which embed JIT compilers to obfuscate at runtime... as far as I know, those are still unsolved problems.
This is a good overview of the subject, but pretty old and doesn't cover "hard" obfuscations: https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=1566145.
https://www.jinyier.me/papers/DATE19_Obf.pdf uses deobfuscation for RTL logic (FGPA/ASIC domain) with SAT solvers. Might be useful for a point of view from a fairly different domain.
https://advising.cs.arizona.edu/~debray/Publications/generic... uses "semantics-preserving transformations" to shed obfuscation. I think this approach is the way to go, especially when combined with dynamic/symbolic analysis to mitigate virt/jit types of transformations.
I'll mention this one as a cautionary tale: https://dl.acm.org/doi/pdf/10.1145/2886012 has some good general info but glosses over the machine learning approach. It considers Hex-rays' FLIRT to be "machine learning", but FLIRT just hashes signatures, can be spoofed (i.e. https://siliconpr0n.org/uv/issues_with_flirt_aware_malware.p...), and is useless against obfuscation.
Eventually I think SBOM tools like Black Duck[1] and SLSA[2] will incorporate ML to improve the accuracy of even figuring out what dependencies a piece of software actually has.
[1]: https://www.synopsys.com/software-integrity/software-composi...
[2]: https://slsa.dev/
-
10 reasons you should quit your HTTP client
The dependency chain is certified! SLSA!
-
UEFI Software Bill of Materials Proposal
The things you mentioned are not solved by a typical "SBOM" but e.g. CycloneDX has extra fields to record provenance and pedigree and things like in-toto (https://in-toto.io/) or SLSA (https://slsa.dev/) also aim to work in this field.
I've spent the last six months in this field and people will tell you that this or that is an industry best practice or "a standard" but in my experience none of that is true. Everyone is still trying to figure out how best to protect the software supply chain security and things are still very much in flux.
-
Gittuf – a security layer for Git using some concepts introduced by TUF
It's multi-pronged and I imagine adopters may use a subset of features. Broadly, I think folks are going to be interested in a) branch/tag/reference protection rules, b) file protection rules (monorepo or otherwise, though monorepos do pose a very apt usecase for gittuf), and c) general key management for those who primarily care about Git signing.
For those who care about a and b, I think the work we want to do to support [in-toto attestations](https://github.com/in-toto/attestation) for [SLSA's upcoming source track](https://github.com/slsa-framework/slsa/issues/956) could be very interesting as well.
- SLSA • Supply-Chain Levels for Software Artifacts
-
Password-stealing Linux malware served for 3 years and no one noticed
It doesn't have to be. Corporations which are FedRAMP[1] compliant, have to build software reproducibly in a fully isolated environment, only from reviewed code.[2]
[1] https://en.wikipedia.org/wiki/FedRAMP
[2] https://slsa.dev/
-
OSCM: The Open Source Consumption Manifesto
SLSA stands for Supply chain Levels for Software Artifacts, and it is a framework that aims to provide a set of best practices for the software supply chain, with a focus on OSS. It was created by Google, and it is now part of the OpenSSF. It consists of four levels of assurance, from Level 1 to Level 4, that correspond to different degrees of protection against supply chain attacks. Our CTO Paolo Mainardi mentioned SLSA in a very good article on software supply chain security, and we also mentioned it in another article about securing OCI Artifacts on Kubernetes.
-
CLOUD SECURITY PODCAST BY GOOGLE - EP116 SBOMs: A Step Towards a More Secure Software Supply Chain -
SLSA.dev
- Supply Chain Levels for Software Artifacts (SLSA)
What are some alternatives?
gallery - Flutter Gallery was a resource to help developers evaluate and use Flutter
grype - A vulnerability scanner for container images and filesystems
valence-native - A React environment for cross platform desktop apps
DependencyCheck - OWASP dependency-check is a software composition analysis utility that detects publicly disclosed vulnerabilities in application dependencies.
vim-iced - Clojure Interactive Development Environment for Vim8/Neovim
trivy - Find vulnerabilities, misconfigurations, secrets, SBOM in containers, Kubernetes, code repositories, clouds and more
babashka - Native, fast starting Clojure interpreter for scripting
sig-security - 🔐CNCF Security Technical Advisory Group -- secure access, policy control, privacy, auditing, explainability and more!
language - Design of the Dart language
checkov - Prevent cloud misconfigurations and find vulnerabilities during build-time in infrastructure as code, container images and open source packages with Checkov by Bridgecrew.
pack - CLI for building apps using Cloud Native Buildpacks
jspolicy - jsPolicy - Easier & Faster Kubernetes Policies using JavaScript or TypeScript