frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

Open in hackernews

Show HN: COSS – Open-Source Standard with AI-Readable Project Metadata

https://www.contriboss.com
2•seuros•7h ago

Comments

seuros•7h ago
Hi HN! I'm sharing COSS (Contribution Open Source Standard) addressing two big problems: vendor lock-in and AI computational waste.

  The AI angle: Current AI tools waste enormous compute re-analyzing the same project patterns. "Is this Python or Node?", "What's the build
  command?", "Where are the tests?" They hallucinate answers instead of reading structured metadata.

  COSS includes a comprehensive coss.toml format for this:
  ```toml
  name = "my-project"
  languages = ["Rust", "JavaScript", "Python"]
  project_type = "web-application"

  [frameworks]
  backend = { name = "Rails", version = "8.0.2" }
  frontend = { name = "Next.js", version = "13.2.1" }

  build = "make build"
  test = "make test"
  lint = "eslint --config .eslintrc.yaml"

  [test_frameworks]
  javascript = "jest --ci"
  rust = "cargo test --all"

  [dependency_locks]
  javascript = "yarn.lock"
  rust = "Cargo.lock"

  This helps AI tools understand your project instantly with one sweep, no more guessing at build commands or test frameworks. It covers everything from languages
  and dependencies to security scanning and documentation coverage.

  Important note: The spec is not final yet, contributions and feedback are very welcome! We want to get this right before wider adoption.

  The broader problem: Too many "open source" projects have hidden vendor dependencies or lock-in mechanisms. COSS defines 5 principles for truly
  neutral software:
  • Universal Access • Anti-Vendor Lock-in • Optional Dependencies • Modular Scope • Contributor Ethics

  It's not a license, it's a standard and mark signaling genuine openness.

  Benefits:
  • Faster, more accurate AI coding assistance
  • Reduced AI computational waste across the ecosystem
  • Protection from vendor traps
  • Better project discoverability and cataloging

  Would love HN's feedback. Do you see AI tools struggling with basic project understanding? Have you hit vendor lock-in pain points? What metadata
  fields would be most valuable?

  Template: https://www.contriboss.com/coss.v0.0.1.toml
  Discussions: https://github.com/contriboss/discussions