Comparison
do-not-answer vs chatgpt-plugin-eval
Verdict
Pick do-not-answer if dataset for evaluating safeguards in LLMs to ensure ethical compliance, distributed under both Creative Commons and Apache licenses; pick chatgpt-plugin-eval if chatgpt-plugin-eval is an evaluation framework designed specifically to assess security, privacy, and safety concerns related to third-party plugins interfacing with large language models like ChatGPT.
Markdown twin · do-not-answer alternatives · chatgpt-plugin-eval alternatives
GraphCanon updated 2w
vs
Trust & integrity
| Signal | do-not-answer | chatgpt-plugin-eval |
|---|---|---|
| Maintenance | Dormant (788d since push) As of 2w · github_public_v1 | Dormant (736d since push) As of 2w · github_public_v1 |
| Provenance | Not a fork · Organization account As of 2w · github_public_v1 | Not a fork · Organization account As of 2w · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No lockfile (source not queried) As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- do-not-answer
- A Dataset for Evaluating Safeguards in LLMs
- chatgpt-plugin-eval
- Framework for Evaluating Security in LLM Plugin Ecosystems
Stars
- do-not-answer
- 339
- chatgpt-plugin-eval
- 29
Forks
- do-not-answer
- 29
- chatgpt-plugin-eval
- 7
Open issues
- do-not-answer
- 0
- chatgpt-plugin-eval
- 1
Language
- do-not-answer
- Jupyter Notebook
- chatgpt-plugin-eval
- HTML
Adopt for
- do-not-answer
- Dataset for evaluating safeguards in LLMs to ensure ethical compliance, distributed under both Creative Commons and Apache licenses.
- chatgpt-plugin-eval
- chatgpt-plugin-eval is an evaluation framework designed specifically to assess security, privacy, and safety concerns related to third-party plugins interfacing with large language models like ChatGPT.
Persona
- do-not-answer
- -
- chatgpt-plugin-eval
- -
Runtime
- do-not-answer
- -
- chatgpt-plugin-eval
- -
License
- do-not-answer
- Dual licensing model, datasets under Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License and source files under Apache 2.0 license.
- chatgpt-plugin-eval
- The license information for chatgpt-plugin-eval is unknown.
Last pushed
- do-not-answer
- Jun 7, 2024
- chatgpt-plugin-eval
- Jul 29, 2024
Categories
- do-not-answer
- Evaluation & Observability
- chatgpt-plugin-eval
- Evaluation & Observability
Trust and health
Days since push
- do-not-answer
- 788d
- chatgpt-plugin-eval
- 736d
Open issues (now)
- do-not-answer
- 0
- chatgpt-plugin-eval
- 1
Full report
- do-not-answer
- Trust report
- chatgpt-plugin-eval
- Trust report
Choose do-not-answer if…
- do-not-answer is primarily Jupyter Notebook; chatgpt-plugin-eval is HTML.
- Tags unique to do-not-answer: datasets, ethical ai, llm-evaluation, safeguard testing.
- To assess the reliability of safeguards implemented in your Large Language Model.
When NOT to use do-not-answer
- If you require tools for direct implementation or fine-tuning LLMs rather than evaluating them.
- Your project does not involve assessing ethical compliance or safeguard measures within language models.
Choose chatgpt-plugin-eval if…
- chatgpt-plugin-eval is primarily HTML; do-not-answer is Jupyter Notebook.
- Tags unique to chatgpt-plugin-eval: chatgpt, llm-plugins, privacy, security.
- - When evaluating the security risks of integrating third-party services into your LLM platform through plugins
When NOT to use chatgpt-plugin-eval
- - In cases where only generic, high-level security guidance is required without an in-depth framework analysis
- - When the primary focus is on improving performance metrics rather than addressing specific security and privacy concerns of LLM plugins
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (Libr-AI/do-not-answer) · observed Aug 5, 2026
- GitHub forks (Libr-AI/do-not-answer) · observed Aug 5, 2026
- Last push (Libr-AI/do-not-answer) · observed Jun 7, 2024
- License file (Apache-2.0) · observed Aug 5, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (llm-platform-security/chatgpt-plugin-eval) · observed Aug 5, 2026
- GitHub forks (llm-platform-security/chatgpt-plugin-eval) · observed Aug 5, 2026
- Last push (llm-platform-security/chatgpt-plugin-eval) · observed Jul 29, 2024
- License file (unknown) · observed Aug 5, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: do-not-answer 339 · chatgpt-plugin-eval 29 (synced Aug 5, 2026).
Common questions
- What is the difference between do-not-answer and chatgpt-plugin-eval?
- do-not-answer: A Dataset for Evaluating Safeguards in LLMs. chatgpt-plugin-eval: Framework for Evaluating Security in LLM Plugin Ecosystems. See the comparison table for live GitHub stats and shared categories.
- When should I choose do-not-answer over chatgpt-plugin-eval?
- Choose do-not-answer over chatgpt-plugin-eval when do-not-answer is primarily Jupyter Notebook; chatgpt-plugin-eval is HTML; Tags unique to do-not-answer: datasets, ethical ai, llm-evaluation, safeguard testing; To assess the reliability of safeguards implemented in your Large Language Model.
- When should I choose chatgpt-plugin-eval over do-not-answer?
- Choose chatgpt-plugin-eval over do-not-answer when chatgpt-plugin-eval is primarily HTML; do-not-answer is Jupyter Notebook; Tags unique to chatgpt-plugin-eval: chatgpt, llm-plugins, privacy, security; - When evaluating the security risks of integrating third-party services into your LLM platform through plugins.
- When should I avoid do-not-answer?
- If you require tools for direct implementation or fine-tuning LLMs rather than evaluating them. Your project does not involve assessing ethical compliance or safeguard measures within language models.
- When should I avoid chatgpt-plugin-eval?
- - In cases where only generic, high-level security guidance is required without an in-depth framework analysis - When the primary focus is on improving performance metrics rather than addressing specific security and privacy concerns of LLM plugins
- Is do-not-answer or chatgpt-plugin-eval more popular on GitHub?
- do-not-answer has more GitHub stars (339 vs 29). Stars measure visibility, not whether either tool fits your constraints.
- Are do-not-answer and chatgpt-plugin-eval open source?
- Yes - both are open-source projects on GitHub.
- Where can I find alternatives to do-not-answer or chatgpt-plugin-eval?
- GraphCanon lists graph-backed alternatives at do-not-answer alternatives and chatgpt-plugin-eval alternatives (do-not-answer markdown twin, chatgpt-plugin-eval markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, do-not-answer or chatgpt-plugin-eval?
- do-not-answer: Dormant. chatgpt-plugin-eval: Dormant. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for do-not-answer and chatgpt-plugin-eval?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: do-not-answer trust report; chatgpt-plugin-eval trust report.