Item detail
github.com

ShieldNet-360/prompt-gate

RepoRadar surfaced ShieldNet-360/prompt-gate — a developer tool — into the AI Safety section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.1 out of 10.

Score8.0
Popularity16.0
Riskconditional
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum6.0
Maturity6.2
Open-source/build8.4
Evidence8.0
Workflow potential9.1
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for teams that want practical guardrails around what users and agents can paste into AI tools without turning prompt security into another hosted data leak.

Who should use it

Security teams building local guardrails around employee or agent use of AI tools Developers who want on-device secret and PII checks before content reaches remote LLMs Operators comparing DNS- and extension-based controls against cloud DLP services Teams evaluating how to separate approved AI usage from blocked AI usage on managed desktops

Who should skip it

Pass on ShieldNet-360/prompt-gate if you need something non-technical and turnkey rather than a tool that requires comfort with CLI, dependencies, or system configuration.

About this signal

ShieldNet-360/prompt-gate is tracked by RepoRadar as a developer tool in the AI Safety section. First seen 2026-06-27; the source record was last checked on 2026-06-27. The current verdict is 'try now' with a Gold tier and hard setup difficulty. The standout signals for ShieldNet-360/prompt-gate are workflow potential (9.1) and open-source/build quality (8.4), while setup ease (4.2) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The ShieldNet-360/prompt-gate record combines a 8.0/10 composite score with separate popularity (16.0), risk (conditional), and setup (hard) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

The product sits in the path of live AI traffic and local DNS resolution, so misconfiguration can block normal workflows or create trust-boundary confusion; If you enable the optional local proxy for non-browser traffic, review the TLS interception and certificate path carefully before you use it beyond a test machine; Because the tool inspects AI-bound content for secrets and PII, teams should document exactly which destinations are allowed, inspected, or blocked before rollout.

Evidence links
Closest alternatives / related signals
dlp ai-safety privacy dns browser-extension secret-scanning mit security
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

38 dated snapshots retained from 2026-06-27 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.0 current · +0.0 net
Repository momentum9.0 current · +3.0 net
GitHub stars (observed)48 current · +4 net
GitHub stars48 exact observation
Versionv1.1.1
Last release2026-07-31T09:59:41Z
Maintenanceactive
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.09.048conditionaltry nowactive
2026-08-128.09.048conditionaltry nowactive
2026-08-118.09.348conditionaltry nowactive
2026-08-108.09.045conditionaltry nowactive
2026-08-098.09.045conditionaltry nowactive
2026-08-088.09.045conditionaltry nowactive
2026-08-078.09.045conditionaltry nowactive
2026-08-068.06.0Not recordedconditionaltry nownot recorded
2026-08-058.06.0Not recordedconditionaltry nownot recorded
2026-08-048.09.045conditionaltry nowactive
2026-08-038.09.045conditionaltry nowactive
2026-08-028.09.045conditionaltry nowactive

Why the record changed

stars changed

Stars changed: 45 → 48.

stars changed

Stars changed: 44 → 45.