{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihy47vq6co5k7jnvyuzsafbgscdrtph6xdb6anwhfbc4gy4fwreva",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mhuewwirspa2"
  },
  "path": "/t/introducing-l-bom-and-gui-bom/174609#post_1",
  "publishedAt": "2026-03-25T03:31:06.000Z",
  "site": "https://discuss.huggingface.co",
  "tags": [
    "L-BOM",
    "GUI-BOM"
  ],
  "textContent": "Hi everyone, I’m fairly new to sharing things here on HF, but have been around the OSS world for a while. I’ve been working on some various projects over the past few months, and it became clear that there needed to be a better way to examine the contents gguf and safetensors files.\n\n# L-BOM and GUI-BOM\n\nThat’s why I created L-BOM, a lightweight python application that creates a Software Bill of Materials for .gguf and .safetensors files. Because honestly we could all use a chance to look under the hood sometimes, and also people really should know what’s in the models they are embedding.\n\nBut really, I wanted to make sure that the transparency of having a SBOM was available to everyone, not just those of us who write code. So I also created GUI-BOM, which is L-BOM on the inside, Docker container or .bat file on the outside. GUI-BOM wraps L-BOM up in a nice local webpage that allows people of any skill level to use L-BOM to obtain transparency of their .gguf and .safetensors files.\n\n## Contributing\n\nBoth L-BOM and GUI-BOM are open source, and maintained through repo’s on my Github. Suggestions and contributions are welcome.",
  "title": "Introducing L-BOM and GUI-BOM"
}