kaitai_struct_formats
osv.dev
Our great sponsors
| kaitai_struct_formats | osv.dev | |
|---|---|---|
| 3 | 19 | |
| 682 | 1,405 | |
| 0.7% | 4.1% | |
| 6.3 | 9.7 | |
| 13 days ago | 2 days ago | |
| Kaitai Struct | Python | |
| - | Apache License 2.0 |
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.
kaitai_struct_formats
- Magika: AI powered fast and efficient file type identification
-
Fq: Jq for Binary Formats
Kaitai has a repository of binary formats[1] that can be used in visualizers or to auto-generate parsers.
[1] https://formats.kaitai.io/
-
Show HN: I am building a new Python library to read/write PDF files
This is tangential to your submission, but PDF is the file format I use for exercising any library that claims to be a declarative file format (ala https://github.com/kaitai-io/kaitai_struct_formats#readme )
osv.dev
-
Magika: AI powered fast and efficient file type identification
Is it safe to assume that hashing (1) every file on disk, or (2) any given file on disk at random, will yield random bits with uniform probability; and (3) why Argon2 instead of e.g. only two rounds of SHA256?
https://github.com/google/osv.dev/blob/master/README.md#usin... :
> We provide a Go based tool that will scan your dependencies, and check them against the OSV database for known vulnerabilities via the OSV API. ... With package metadata, not (a file hash, package) database that could be generated from OSV and the actual package files instead of their manifest of already-calculated checksums.
Might as well be heating a pool on the roof with all of this waste heat from hashing binaries build from code of unknown static and dynamic quality.
Add'l useful formats:
> Currently it is able to scan various lockfiles, debian docker containers, SPDX and CycloneDB SBOMs, and git repositories
-
Dependabot vs RenovateBot
Also it supports an alternative sources of CVEs with https://osv.dev
-
Pyscan: A command-line tool to detect security issues in your python dependencies.
https://osv.dev its open source and even has a free API with almost all the popular languages. One of the inspirations for my project.
-
Announcing Pyscan: A dependency vulnerability scanner for python projects.
pyscan uses OSV as its database for now. There are plans to add a few more.
-
We should start to add “ai.txt” as we do for “robots.txt”
JSON-LD or RDFa (RDF in HTML attributes) in at least the /index.html the HTML footer should be sufficient to indicate that there is structured linked data metadata for crawlers that then don't need an HTTP request to a .well-known URL /.well-known/ai_security_reproducibility_carbon.txt.jsonld.json
OSV is a new format for reporting security vulnerabilities like CVEs and an HTTP API for looking up CVEs from software component name and version. https://github.com/google/osv.dev#third-party-tools-and-inte... :
> We provide a Go based tool that will scan your dependencies, and check them against the OSV database for known vulnerabilities via the OSV API.
> Currently it is able to scan various lockfiles, -- (repo2docker REES config files) -- debian docker containers, SPDX and CycloneDB SBOMs, and git repositories.
-
Ask HN: Most interesting tech you built for just yourself?
Something I've recently worked on is building an SQLite database of all the dependencies my organisation uses, which makes it possible to write our own queries and reports. The tool is all Open Source (https://dmd.tanna.dev) and has a CLI as well as the SQLite data.
Ive used it to look for software that's out of date (via https://endoflife.date), to find vulnerablilities (via https://osv.dev) and get license information (via https://deps.dev)
It's been hugely useful for us understanding use of internal and external dependencies, and I wish I'd built it earlier in my career so I could've had it for other companies I've worked at!
-
Malicious library inits?
Something like osv-scanner (https://osv.dev/), Github's depandabot etc would help to a great extend in detecting malicious dependencies. Not much else be done I guess
- Distributed vulnerability database for Open Source
- SBOM and dependencies check tool and vulnerabilities database from Google
-
Free tool for generating SBOM and CVEs against source or binaries
Have a look at https://security.googleblog.com/2022/12/announcing-osv-scanner-vulnerability.html they have plans for c++ https://github.com/google/osv.dev/issues/783
What are some alternatives?
PyMuPDF - PyMuPDF is a high performance Python library for data extraction, analysis, conversion & manipulation of PDF (and other) documents.
osv-scanner - Vulnerability scanner written in Go which uses the data provided by https://osv.dev
pdfquery - A fast and friendly PDF scraping library.
certspotter - Certificate Transparency Log Monitor
cutter - Free and Open Source Reverse Engineering Platform powered by rizin
betterscan-ce - Code Scanning/SAST/Static Analysis/Linting using many tools/Scanners + OpenAI GPT with One Report (Code, IaC) - Betterscan Community Edition (CE)
jqjq - jq implementation of jq
Awesome-Fuzzing - A curated list of fuzzing resources ( Books, courses - free and paid, videos, tools, tutorials and vulnerable applications to practice on ) for learning Fuzzing and initial phases of Exploit Development like root cause analysis.
i7j-rups - RUPS is an acronym for Reading and Updating PDF Syntax. RUPS is a tool built on top of iText® that allows you to look inside a PDF document and browse the different PDF objects and content streams.
certificate-transparency-go - Auditing for TLS certificates (Go code)
pdfplumber - Plumb a PDF for detailed information about each char, rectangle, line, et cetera — and easily extract text and tables.
tincan-tls - A cleanroom implementation of TLS 1.3