Source Mailchimp est-il sûr ?

Source Mailchimp — Nerq Trust Score 59.9/100 (Note D). Score basé sur 5 independent trust signals.

Source Mailchimp est un software tool avec un Nerq Trust Score de 59.9/100 (D), basé sur 5 dimensions de données indépendantes. Sécurité: 0/100. Maintenance: 0/100. Popularité: 0/100. Données de plusieurs sources publiques dont les registres de paquets, GitHub, NVD, OSV.dev et OpenSSF Scorecard. Dernière mise à jour: n/a. Données lisibles par machine (JSON).

Source Mailchimp est-il sûr ?

Détail du score de confiance — Source Mailchimp has a Nerq Trust Score of 59.9/100 (D). Measured across 5 independent trust signals.

Analyse de Sécurité → Rapport de confidentialité de Source Mailchimp →

Quel est le score de confiance de Source Mailchimp ?

Source Mailchimp a un Score de Confiance Nerq de 59.9/100, obtenant la note D. Ce score est basé sur 5 dimensions mesurées indépendamment.

Sécurité
0
Conformité
100
Maintenance
0
Documentation
0
Popularité
0

Quels sont les résultats de sécurité clés pour Source Mailchimp ?

Le signal le plus fort de Source Mailchimp est conformité à 100/100. Aucune vulnérabilité connue n'a été détectée.

⚠Score de sécurité: 0/100 (faible)
⚠Maintenance: 0/100 — faible activité de maintenance
⚠Conformité: 100/100 — covers 52 of 52 jurisdictions
⚠Documentation: 0/100 — documentation limitée
⚠Popularité: 0/100 — adoption communautaire

Qu'est-ce que Source Mailchimp et qui le maintient ?

Auteurairbyte
CatégorieUncategorized
Sourcehttps://hub.docker.com/r/airbyte/source-mailchimp
Protocolsdocker

Conformité réglementaire

EU AI Act Risk ClassNot assessed
Compliance Score100/100
JurisdictionsAssessed across 52 jurisdictions

Source Mailchimp sur d'autres plateformes

Même développeur/entreprise dans d'autres registres :

airbyte-cdk
77/100 · pypi
airbyte-source-declarative-manifest
75/100 · pypi
airbyte-api
72/100 · pypi
airbyte-source-bing-ads
70/100 · pypi
airbyte-source-kyriba
70/100 · pypi

What Is Source Mailchimp?

Source Mailchimp is a software tool in the uncategorized category available on docker_hub. Nerq Trust Score: 60/100 (D).

Nerq independently analyzes every software tool, app, and extension across multiple trust signals including sécurité vulnerabilities, maintenance activity, license conformité, and adoption par la communauté.

How Nerq Assesses Source Mailchimp's Safety

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

The overall Trust Score of 59.9/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 Source Mailchimp?

Source Mailchimp is commonly evaluated by:

How to read the signals: Source Mailchimp's measured signals (sécurité 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 Source Mailchimp's Safety Yourself

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

  1. Check the source code — Examiner le/la repository sécurité 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 Source Mailchimp's dependency tree.
  3. Avis permissions — Understand what access Source Mailchimp requires. Software tools should follow the principle of least privilege.
  4. Test in isolation — Run Source Mailchimp 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=source-mailchimp
  6. Examiner le/la license — Confirm that Source Mailchimp'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 sécurité concerns openly. Low community engagement may indicate limited peer review of the codebase.

Common Safety Concerns with Source Mailchimp

When evaluating whether Source Mailchimp is safe, consider these category-specific risks:

Data handling

Understand how Source Mailchimp processes, stores, and transmits your data. Examiner le/la tool's privacy policy and data retention practices, especially for sensitive or proprietary information.

Dependency sécurité

Check Source Mailchimp's dependency tree for known vulnerabilities. Tools with outdated or unmaintained dependencies pose a higher sécurité risk.

Update frequency

Regularly check for updates to Source Mailchimp. Sécurité patches and bug fixes are only effective if you're running the latest version.

Third-party integrations

If Source Mailchimp 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 conformité

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

Best Practices for Using Source Mailchimp Safely

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

Conduct regular audits

Periodically review how Source Mailchimp is used in your workflow. Check for unexpected behavior, permissions drift, and conformité with your sécurité policies.

Keep dependencies updated

Ensure Source Mailchimp and all its dependencies are running the latest stable versions to benefit from sécurité patches.

Follow least privilege

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

Monitor for sécurité advisories

Subscribe to Source Mailchimp's sécurité 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 Source Mailchimp is used within your organization, including data handling guidelines and acceptable use cases.

Situations That Warrant Independent Review of Source Mailchimp

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

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

How Source Mailchimp 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. Source Mailchimp's score of 59.9/100 is near the category average of 62/100.

This places Source Mailchimp in line with the typical uncategorized tool tool. It meets baseline expectations but does not distinguish itself from peers on trust metrics.

Industry benchmarks matter because they contextualize a tool's safety profile. A score that looks modéré 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 Source Mailchimp 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, Source Mailchimp'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 sécurité and quality. Conversely, a downward trend may signal reduced maintenance, growing technical debt, or unresolved vulnerabilities. To track Source Mailchimp's score over time, use the Nerq API: GET nerq.ai/v1/preflight?target=source-mailchimp&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 — sécurité, maintenance, documentation, conformité, and community — has evolved independently, providing granular visibility into which aspects of Source Mailchimp are strengthening or weakening over time.

Points Essentiels

Questions fréquentes

Source Mailchimp est-il sûr ?
source-mailchimp avec un Nerq Trust Score de 59.9/100 (D). Signal le plus fort : conformité (100/100). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100).
Quel est le score de confiance de Source Mailchimp ?
source-mailchimp: 59.9/100 (D). Score basé sur Sécurité (0/100), Maintenance (0/100), Popularité (0/100), Documentation (0/100). Compliance: 100/100. Les scores sont mis à jour lorsque de nouvelles données sont disponibles. API: GET nerq.ai/v1/preflight?target=source-mailchimp
Quelles sont les alternatives plus sûres à Source Mailchimp ?
Dans la catégorie Uncategorized, d'autres software tool sont en cours d'analyse — revenez bientôt. source-mailchimp scores 59.9/100.
À quelle fréquence le score de sécurité de Source Mailchimp est-il mis à jour ?
Nerq recomputes Source Mailchimp's trust score as new data becomes available. Current: 59.9/100 (D). API: GET nerq.ai/v1/preflight?target=source-mailchimp
Puis-je utiliser Source Mailchimp dans un environnement réglementé ?
Source Mailchimp: 59.9/100 (D). Compliance: 52 of 52 jurisdictions. Evaluate against your own regulatory requirements.
API: /v1/preflight Trust Badge API Docs

Voir aussi

Disclaimer: Les scores de confiance Nerq sont des évaluations automatisées basées sur des signaux publiquement disponibles. Ce ne sont pas des recommandations ou des garanties. Effectuez toujours votre propre vérification.

Nous utilisons des cookies pour l'analyse et le cache. Confidentialité