Graphene VS Deadpendency

• Run unmodified applications in SGX enclaves
  Graphene is a library OS that lets existing Linux applications (e.g. Nginx, Redis, PyTorch, Python) run inside Intel SGX enclaves with little or no source code change. This greatly reduces the effort of adopting confidential computing.
• Strong confidentiality and integrity guarantees
  Running workloads in hardware-protected enclaves shields code and data from the host OS, hypervisor, and cloud provider. This suits sensitive workloads in untrusted or multi-tenant environments.
• Small trusted computing base
  As a lightweight library OS, it implements Linux functionality in user space and exposes a narrow host interface. This reduces the attack surface compared with running a full OS or a heavy VM inside the trusted boundary.
• Broad Linux compatibility
  It supports multi-process applications (fork, IPC), threading, and a wide range of Linux syscalls. This allows complex real-world workloads, not just toy examples, to be ported.
• Open source with a research pedigree
  The project is open source (LGPL) and grew out of academic and industry research. Its design is well documented and can be audited, studied, and extended.

Possible disadvantages

• Tied to specific hardware
  The main use case relies on Intel SGX, which is only available on certain CPUs. Intel has deprecated SGX on consumer processors, which limits where it can be deployed.
• Performance overhead
  Enclave transitions, memory encryption, and limited enclave page cache (EPC) size can slow I/O-heavy or memory-hungry workloads. Performance tuning is often needed.
• Complex setup and configuration
  Users must write manifest files, handle file hashes, sign enclaves, and set up remote attestation. This requires SGX expertise and has a steep learning curve.
• Incomplete syscall and feature coverage
  Not every Linux feature or syscall is supported, so some applications need workarounds or will not run. Debugging inside enclaves is also harder.
• Project renamed and superseded
  The project continued under the name Gramine, so the original Graphene branding and site may be outdated or less actively maintained. Users should check which version is current and supported.

• Automated Dependency Monitoring
  Deadpendency automatically checks your project's dependencies for signs of being dead, unmaintained, or deprecated, saving developers from manually tracking the health of each dependency.
• GitHub Integration
  Deadpendency integrates directly with GitHub as a GitHub App, making it easy to set up and run as part of your existing pull request and CI workflow without requiring additional infrastructure.
• Early Warning System
  By catching dead or unmaintained dependencies early, Deadpendency helps teams avoid security risks and technical debt that come from relying on abandoned libraries.
• Multi-Language Support
  Deadpendency supports a wide range of programming languages and package ecosystems, making it useful for polyglot projects and diverse development teams.
• Low Configuration Overhead
  The tool is designed to work out of the box with minimal configuration, allowing teams to get value quickly without spending significant time on setup and customization.

Possible disadvantages

• Limited to GitHub
  Deadpendency is primarily a GitHub App, which means teams using other platforms like GitLab or Bitbucket cannot easily use the service without switching or mirroring their repositories.
• Potential False Positives
  The tool may flag dependencies as dead or unmaintained based on activity metrics, even when a library is stable and simply mature, leading to unnecessary concern or migration efforts.
• Niche Use Case
  Dependency health checking is a relatively narrow function. Teams may prefer more comprehensive dependency management tools that also handle vulnerability scanning, license compliance, and version updates in one solution.
• Reliance on External Signals
  Deadpendency relies on external signals like repository activity and release frequency to determine dependency health, which may not always accurately reflect the true maintenance status of a project.
• Limited Community and Ecosystem
  As a relatively niche tool, Deadpendency has a smaller user community compared to alternatives like Dependabot or Renovate, which can mean fewer resources, community support, and third-party integrations.

No analysis of Graphene yet.

Tracking Graphene since Oct 2026.

• Deadpendency Open Sourced

  I created a tiny startup in Haskell which failed RIP. I decided to open source the code though. Source: over 3 years ago

• Twitch Streamers?

  I sometimes stream my Haskell work on deadpendency - https://www.twitch.tv/alistairbuzz. Source: over 5 years ago