Is Demo Time veilig?

Demo Time — Nerq Trust Score 49.0/100 (D-beoordeling). Score gebaseerd op 3 independent trust signals.

Demo Time is een software tool met een Nerq Vertrouwensscore van 49.0/100 (D), based on 3 onafhankelijke gegevensdimensies. Onderhoud: 0/100. Populariteit: 1/100. Gegevens afkomstig van meerdere openbare bronnen waaronder pakketregisters, GitHub, NVD, OSV.dev en OpenSSF Scorecard. Laatst bijgewerkt: n/a. Machineleesbare gegevens (JSON).

Is Demo Time veilig?

Vertrouwensscore details — Demo Time has a Nerq Trust Score of 49.0/100 (D). Measured across 3 independent trust signals.

Beveiligingsanalyse → Demo Time Privacyrapport →

Wat is de vertrouwensscore van Demo Time?

Demo Time heeft een Nerq Trust Score van 49.0/100 met het cijfer D. Deze score is gebaseerd op 3 onafhankelijk gemeten dimensies, waaronder beveiliging, onderhoud en community-adoptie.

Onderhoud
0
Documentatie
0
Populariteit
1

Wat zijn de belangrijkste beveiligingsbevindingen voor Demo Time?

Het sterkste signaal van Demo Time is populariteit met 1/100. Er zijn geen bekende kwetsbaarheden gedetecteerd.

⚠Onderhoud: 0/100 — lage onderhoudsactiviteit
⚠Documentatie: 0/100 — beperkte documentatie
⚠Populariteit: 1/100 — 238 sterren op pulsemcp

Wat is Demo Time en wie onderhoudt het?

Ontwikkelaarhttps://github.com/estruyf/vscode-demo-time
CategorieMarketing
Sterren238
Bronhttps://github.com/estruyf/vscode-demo-time

Populaire alternatieven in marketing

sansan0/TrendRadar
66.6/100 · C
github
srbhr/Resume-Matcher
61.9/100 · C
github
friuns2/BlackFriday-GPTs-Prompts
60.2/100 · C
github
coreyhaines31/marketingskills
63.2/100 · C
github
RayVentura/ShortGPT
58.2/100 · D
github

What Is Demo Time?

Demo Time is a software tool in the marketing category: Interact with Demo Time documentatie and automate presentation demos. It has 238 GitHub stars. Nerq Trust Score: 49/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including beveiliging vulnerabilities, onderhoud activity, license naleving, and gemeenschapsacceptatie.

How Nerq Assesses Demo Time's Safety

Nerq's Trust Score is calculated from 13+ independent signals aggregated into five dimensies. Here is how Demo Time performs in each:

The overall Trust Score of 49.0/100 (D) 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 Demo Time?

Demo Time is commonly evaluated by:

How to read the signals: Demo Time's measured signals (onderhoud 0/100, documentatie 0/100, community 1/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 Demo Time's Safety Yourself

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

  1. Check the source code — Bekijk de repository beveiliging policy, open issues, and recent commits for signs of active onderhoud.
  2. Scan dependencies — Use tools like npm audit, pip-audit, or snyk to check for known vulnerabilities in Demo Time's dependency tree.
  3. Beoordeling permissions — Understand what access Demo Time requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Demo Time 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=Demo Time
  6. Bekijk de license — Confirm that Demo Time'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 beveiliging concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Demo Time

When evaluating whether Demo Time is safe, consider these category-specific risks:

Data handling

Understand how Demo Time processes, stores, and transmits your data. Bekijk de tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency beveiliging

Check Demo Time's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher beveiliging risk.

Update frequency

Regularly check for updates to Demo Time. Beveiliging patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Demo Time 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 naleving

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

Best Practices for Using Demo Time Safely

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

Conduct regular audits

Periodically review how Demo Time is used in your workflow. Check for unexpected behavior, permissions drift, and naleving with your beveiliging policies.

Keep dependencies updated

Ensure Demo Time and all its dependencies are running the latest stable versions to benefit from beveiliging patches.

Follow least privilege

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

Monitor for beveiliging advisories

Subscribe to Demo Time's beveiliging 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 Demo Time is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Demo Time

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

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

How Demo Time Compares to Industry Standards

Nerq indexes over 6 million software tools, apps, and packages across dozens of categories. Among marketing tools, the average Trust Score is 62/100. Demo Time's score of 49.0/100 is below the category average of 62/100.

This suggests that Demo Time trails behind many comparable marketing tools. Organizations with strict beveiliging requirements should evaluate whether higher-scoring alternatives better meet their needs.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks matig 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 Demo Time 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 onderhoud patterns change, Demo Time'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 beveiliging and quality. Conversely, a downward trend may signal reduced onderhoud, growing technical debt, or unresolved vulnerabilities. To track Demo Time's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=Demo Time&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 — beveiliging, onderhoud, documentatie, naleving, and community — has evolved independently, providing granular visibility into which aspects of Demo Time are strengthening or weakening over time.

Demo Time vs Alternatieven

In the marketing category, Demo Time scores 49.0/100. There are higher-scoring alternatives available. For a detailed comparison, see:

Belangrijkste conclusies

Veelgestelde vragen

Is Demo Time veilig?
Demo Time met een Nerq Vertrouwensscore van 49.0/100 (D). Sterkste signaal: populariteit (1/100). Score gebaseerd op Onderhoud (0/100), Populariteit (1/100), Documentatie (0/100).
Wat is de vertrouwensscore van Demo Time?
Demo Time: 49.0/100 (D). Score gebaseerd op Onderhoud (0/100), Populariteit (1/100), Documentatie (0/100). Scores worden bijgewerkt wanneer nieuwe data beschikbaar komen. API: GET nerq.ai/v1/preflight?target=Demo Time
Wat zijn veiligere alternatieven voor Demo Time?
In de categorie Marketing, higher-rated alternatives include sansan0/TrendRadar (67/100), srbhr/Resume-Matcher (62/100), friuns2/BlackFriday-GPTs-Prompts (60/100). Demo Time scores 49.0/100.
Hoe vaak wordt de beveiligingsscore van Demo Time bijgewerkt?
Nerq recomputes Demo Time's trust score as new data becomes available. Current: 49.0/100 (D). API: GET nerq.ai/v1/preflight?target=Demo Time
Kan ik Demo Time gebruiken in een gereguleerde omgeving?
Demo Time: 49.0/100 (D). Compliance signals are shown in the breakdown above. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Zie ook

Disclaimer: Nerq-vertrouwensscores zijn geautomatiseerde beoordelingen op basis van openbaar beschikbare signalen. Ze vormen geen aanbeveling of garantie. Voer altijd uw eigen verificatie uit.

We gebruiken cookies voor analyse en caching. Privacy