Is junit5-ci safe to install?

SaferSkills independently audited junit5-ci (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

ci/SKILL.md · 1 file

ci/SKILL.md2.9 KB · Markdown

name: junit5-ci

description: Use when Codex needs to run JUnit 5 tests through Maven, Gradle, or the Console Launcher, configure CI pipelines, manage tags and reports, or debug environment-specific execution issues.

metadata:

author: jovd83

version: 1.0.0

dispatcher-category: testing

dispatcher-capabilities: ci-configuration, junit5-ci

dispatcher-accepted-intents: configure_junit_ci, optimize_junit_execution

dispatcher-input-artifacts: repo_context, ci_pipeline, build_files

dispatcher-output-artifacts: ci_guidance, execution_plan, pipeline_update

dispatcher-stack-tags: junit5, ci, jvm

dispatcher-risk: medium

dispatcher-writes-files: true

JUnit 5 CI

1. Inspect the Execution Path

Identify whether the repo uses Maven, Gradle, the Console Launcher, or mixed execution paths.
Confirm how tests are filtered, tagged, and reported.
Read references/build-and-run.md before changing pipeline behavior.
Read references/tool-recipes.md when the repo supports more than one execution path.

2. Configure Safely

Use useJUnitPlatform() in Gradle-based execution.
Use current Surefire or Failsafe configuration already established by the repo when possible.
Keep tags, includes, excludes, and reporting explicit.
Use junit-platform.properties for shared execution parameters when the repo already follows that pattern.
Keep local and CI commands aligned unless the repo intentionally separates them.

3. Debug CI Failures

Compare local and CI Java versions.
Compare environment variables, locale, time zone, and file-system assumptions.
Compare build commands and active profiles.
Read references/ci-failure-patterns.md when failures reproduce only in automation.
Read references/tagging-and-reporting.md before changing tag filters or report outputs.

4. Examples

Input: Make these JUnit 5 integration tests run in Maven CI only.

Output: Configure naming, tags, or Failsafe boundaries without breaking fast local feedback.

Input: Gradle discovers no tests.

Output: Verify useJUnitPlatform(), naming conventions, and source-set wiring.

Input: Split fast unit tests from slower integration coverage in Maven.

Output: Use tags, naming, or Surefire/Failsafe boundaries that fit the existing build model.

5. Troubleshooting

Problem: No tests are discovered.

Fix: Check task configuration, naming conventions, and JUnit Platform enablement.

Problem: CI fails but local passes.

Fix: Compare Java version, environment, and execution flags before changing test logic.

Problem: Reports exist locally but not in CI artifacts.

Fix: Check report output paths, pipeline artifact collection, and the actual test task that runs in automation.

junit5-ci— agent skill

Is junit5-ci safe to install?

JUnit 5 CI

1. Inspect the Execution Path

2. Configure Safely

3. Debug CI Failures

4. Examples

5. Troubleshooting

Audit the pieces. Scan the whole. Decide.