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.

Feishu scores 60.0/100 (C+) while temp-env scores 61.8/100 (C+) on the Nerq Trust Score. The two agents are essentially tied on overall trust. Feishu is a uncategorized agent with 0 stars. temp-env is a uncategorized agent with 0 stars.
60.0
C+
Categoryuncategorized
Stars0
Sourceandroid
Security70
Maintenance60
Documentation30
vs
61.8
C+
Categoryuncategorized
Stars0
Sourcecrates
Security90
Maintenance50
Documentation40

Detailed Metric Comparison

Metric Feishu temp-env
Trust Score60.0/10061.8/100
GradeC+C+
Stars00
Categoryuncategorizeduncategorized
Security7090
ComplianceN/AN/A
Maintenance6050
Documentation3040
EU AI Act RiskN/AN/A
VerifiedNoNo

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:

  1. API Compatibility: Feishu (uncategorized) and temp-env (uncategorized) share similar interfaces since they are in the same category.
  2. Security Review: Run a security audit after migration. Check the Feishu safety report and temp-env safety report for known issues.
  3. Testing: Ensure your test suite covers all integration points before switching in production.
  4. Community Support: Feishu has 0 stars and temp-env has 0. Larger communities typically mean better Stack Overflow answers and migration guides.
Feishu Safety Report temp-env Safety Report Feishu Alternatives temp-env Alternatives

Related Pages

Frequently Asked Questions

Which is safer, Feishu or temp-env?
Based on Nerq's independent trust assessment, Feishu has a trust score of 60.0/100 (C+) while temp-env scores 61.8/100 (C+). Both agents are very close in overall trust. Trust scores are based on security, compliance, maintenance, documentation, and community adoption.
How do Feishu and temp-env compare on security?
Feishu has a security score of 70/100 and temp-env scores 90/100. There is a notable difference in their security assessments. Feishu's compliance score is N/A/100 (EU risk: N/A), while temp-env's is N/A/100 (EU risk: N/A).
Should I use Feishu or temp-env?
The choice depends on your requirements. Feishu (uncategorized, 0 stars) and temp-env (uncategorized, 0 stars) serve similar use cases. On trust, Feishu scores 60.0/100 and temp-env scores 61.8/100. Review the full KYA reports for each agent before making a decision. Consider factors like integration requirements, documentation quality (30 vs 40), and maintenance activity (60 vs 50).

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.

We use cookies for analytics and caching. Privacy Policy