Is Last30Days Skill Safe?

Last30Days Skill — Nerq Trust Score 66.8/100 (C grade). Score based on 4 independent trust signals.

Last30Days Skill is a software tool with a Nerq Trust Score of 66.8/100 (C), based on 4 independent data dimensions. Security: 0/100. Maintenance: 0/100. Popularity: 0/100. Data sourced from multiple public sources including package registries, GitHub, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: n/a. Machine-readable data (JSON).

Is Last30Days Skill safe?

Trust Score Breakdown — Last30Days Skill has a Nerq Trust Score of 66.8/100 (C). Measured across 4 independent trust signals.

Security Analysis → Last30Days Skill Privacy Report →

What is Last30Days Skill's trust score?

Last30Days Skill has a Nerq Trust Score of 66.8/100, earning a C grade. This score is based on 4 independently measured dimensions including security, maintenance, and community adoption.

Security
0
Maintenance
0
Documentation
0
Popularity
0

What are the key security findings for Last30Days Skill?

Last30Days Skill's strongest signal is security at 0/100. No known vulnerabilities have been detected.

✗Security score: 0/100 (weak)
✗Maintenance: 0/100 — low maintenance activity
✗Documentation: 0/100 — limited documentation
⚠Popularity: 0/100 — 4,718 stars on github

What is Last30Days Skill and who maintains it?

Authormvanhorn
CategoryUncategorized
Stars4,718
Sourcehttps://github.com/mvanhorn/last30days-skill
Frameworksopenai · anthropic
Protocolsrest

What Is Last30Days Skill?

Last30Days Skill is a software tool in the uncategorized category: AI agent that synthesizes summaries from various social and news platforms.. It has 4,718 GitHub stars. Nerq Trust Score: 67/100 (C).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including security vulnerabilities, maintenance activity, license compliance, and community adoption.

How Nerq Assesses Last30Days Skill's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensions. Here is how Last30Days Skill performs in each:

The overall Trust Score of 66.8/100 (C) is the weighted combination of these measured signals. It is a measurement, not a pass/fail or suitability judgment — weigh the individual signals against your own requirements.

Who Typically Evaluates Last30Days Skill?

Last30Days Skill is commonly evaluated by:

How to read the signals: Last30Days Skill's measured signals (security 0/100, maintenance 0/100, documentation 0/100, community 0/100) are shown above. These are measurements, not a suitability judgment — weigh each signal against the requirements of your own use case and risk tolerance.

How to Verify Last30Days Skill's Safety Yourself

While Nerq provides automated trust analysis, we recommend these additional steps before adopting any software tool:

  1. Check the source code — Review the repository's security policy, open issues, and recent commits for signs of active maintenance.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Last30Days Skill's dependency tree.
  3. Review permissions — Understand what access Last30Days Skill requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Last30Days Skill in a sandboxed environment before granting access to production data or systems.
  5. Monitor continuously — Use Nerq's API to set up automated trust checks: GET nerq.ai/v1/preflight?target=last30days-skill
  6. Review the license — Confirm that Last30Days Skill's license is compatible with your intended use case. Pay attention to restrictions on commercial use, redistribution, and derivative works. Some AI tools use dual licensing or have separate terms for enterprise customers that differ from the open-source license.
  7. Check community signals — Look at the project's issue tracker, discussion forums, and social media presence. A healthy community actively reports bugs, contributes fixes, and discusses security concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Last30Days Skill

When evaluating whether Last30Days Skill is safe, consider these category-specific risks:

Data handling

Understand how Last30Days Skill processes, stores, and transmits your data. Review the tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency security

Check Last30Days Skill's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher security risk.

Update frequency

Regularly check for updates to Last30Days Skill. Security patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Last30Days Skill connects to external APIs or services, each integration point is a potential attack surface. Audit all third-party connections, verify that data shared with external services is minimized, and ensure that integration credentials are rotated regularly.

License and IP compliance

Verify that Last30Days Skill's license is compatible with your intended use case. Some AI tools have restrictive licenses that limit commercial use, redistribution, or derivative works. Using Last30Days Skill in violation of its license can expose your organization to legal liability.

Best Practices for Using Last30Days Skill Safely

Whether you're an individual developer or an enterprise team, these practices will help you get the most from Last30Days Skill while minimizing risk:

Conduct regular audits

Periodically review how Last30Days Skill is used in your workflow. Check for unexpected behavior, permissions drift, and compliance with your security policies.

Keep dependencies updated

Ensure Last30Days Skill and all its dependencies are running the latest stable versions to benefit from security patches.

Follow least privilege

Grant Last30Days Skill only the minimum permissions it needs to function. Avoid granting admin or root access.

Monitor for security advisories

Subscribe to Last30Days Skill's security advisories and vulnerability disclosures. Use Nerq's API to get automated trust score updates.

Document usage policies

Create and maintain a clear policy for how Last30Days Skill is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Last30Days Skill

Nerq's signals are one input. In the following situations, evaluate Last30Days Skill's measured signals against your own requirements before making a decision:

For each situation, compare Last30Days Skill's measured trust score of 66.8/100 and its individual signals against your organization's own criteria. Nerq does not assert whether Last30Days Skill is suitable for any particular use.

How Last30Days Skill Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among uncategorized tools, the average Trust Score is 62/100. Last30Days Skill's score of 66.8/100 is above the category average of 62/100.

This positions Last30Days Skill favorably among uncategorized tools. While it outperforms the average, there is still room for improvement in certain trust dimensions.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks moderate in isolation may actually represent strong performance within a challenging category — or vice versa. Nerq's category-relative analysis helps teams make informed decisions by showing not just absolute quality, but how a tool ranks against its direct peers.

Trust Score History

Nerq continuously monitors Last30Days Skill and recalculates its Trust Score as new data becomes available. Our scoring engine ingests real-time signals from source repositories, vulnerability databases (NVD, OSV.dev), package registries, and community metrics. When a new CVE is published, a major release ships, or maintenance patterns change, Last30Days Skill's score is updated within 24 hours.

Historical trust trends reveal whether a tool is improving, stable, or declining over time. A tool that consistently maintains or improves its score demonstrates ongoing commitment to security and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Last30Days Skill's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=last30days-skill&include=history

Nerq retains trust score snapshots at regular intervals, enabling trend analysis across weeks and months. Enterprise users can access detailed historical reports showing how each dimension — security, maintenance, documentation, compliance, and community — has evolved independently, providing granular visibility into which aspects of Last30Days Skill are strengthening or weakening over time.

Key Takeaways

Frequently Asked Questions

Is Last30Days Skill Safe?
last30days-skill with a Nerq Trust Score of 66.8/100 (C). Strongest signal: security (0/100). Score based on Security (0/100), Maintenance (0/100), Popularity (0/100), Documentation (0/100).
What is Last30Days Skill's trust score?
last30days-skill: 66.8/100 (C). Score based on Security (0/100), Maintenance (0/100), Popularity (0/100), Documentation (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=last30days-skill
What are safer alternatives to Last30Days Skill?
In the Uncategorized category, more software tools are being analyzed — check back soon. last30days-skill scores 66.8/100.
How often is Last30Days Skill's safety score updated?
Nerq recomputes Last30Days Skill's trust score as new data becomes available. Current: 66.8/100 (C). API: GET nerq.ai/v1/preflight?target=last30days-skill
Can I use Last30Days Skill in a regulated environment?
Last30Days Skill: 66.8/100 (C). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

See Also

Disclaimer: Nerq trust scores are automated measurements based on publicly available signals. They are not endorsements, verdicts, or guarantees of suitability. Always evaluate the signals against your own requirements.

We use cookies for analytics and caching. Privacy