Feishu vs temp-env — Trust Score Comparison
Side-by-side trust comparison of Feishu and temp-env. Scores based on security, compliance, maintenance, popularity, and ecosystem signals.
Detailed Metric Comparison
| Metric | Feishu | temp-env |
|---|---|---|
| Trust Score | 60.0/100 | 61.8/100 |
| Grade | C+ | C+ |
| Stars | 0 | 0 |
| Category | uncategorized | uncategorized |
| Security | 70 | 90 |
| Compliance | N/A | N/A |
| Maintenance | 60 | 50 |
| Documentation | 30 | 40 |
| EU AI Act Risk | N/A | N/A |
| Verified | No | No |
Verdict
Feishu (60.0) and temp-env (61.8) have nearly identical trust scores. Both are solid choices. The decision should come down to your specific use case, team preferences, and integration requirements rather than trust differences.
Detailed Analysis
Security
temp-env leads on security with a score of 90/100 compared to Feishu's 70/100. This score reflects dependency vulnerability analysis, known CVE exposure, and security best practices. A higher security score means fewer known vulnerabilities and better security hygiene in the codebase.
Maintenance & Activity
Feishu demonstrates stronger maintenance activity (60/100 vs 50/100). This metric captures commit frequency, issue response times, and release cadence. Actively maintained tools receive faster security patches and are less likely to accumulate technical debt.
Documentation
temp-env has better documentation (40/100 vs 30/100). Good documentation reduces onboarding time and helps teams adopt the tool safely. This score evaluates README completeness, API documentation, code examples, and tutorial availability.
Community & Adoption
Feishu has 0 GitHub stars while temp-env has 0. Both tools have comparable community sizes, suggesting similar levels of ecosystem support and third-party resources.
When to Choose Each Tool
Choose Feishu if you need:
- More actively maintained with faster release cadence
Choose temp-env if you need:
- Higher overall trust score — more reliable for production use
- Stronger security profile with fewer known vulnerabilities
- Better documentation for faster onboarding
Switching from Feishu to temp-env (or vice versa)
When migrating between Feishu and temp-env, consider these factors:
- API Compatibility: Feishu (uncategorized) and temp-env (uncategorized) share similar interfaces since they are in the same category.
- Security Review: Run a security audit after migration. Check the Feishu safety report and temp-env safety report for known issues.
- Testing: Ensure your test suite covers all integration points before switching in production.
- Community Support: Feishu has 0 stars and temp-env has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
Related Pages
Frequently Asked Questions
Related Comparisons
Last updated: 2026-07-21 | Data refreshed weekly
Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.