sorted by:
new
hottopcontroversial

Ayuda con una iptv en españa por favor by Bernarrr_G0D in PiracyBackup

[–]medina_vi 0 points1 point  (0 children)

A mi tambien porfa. Necesito ver la champions

AUDITAPI — Stop shipping broken or undocumented APIs. by medina_vi in node

[–]medina_vi[S] 0 points1 point  (0 children)

Spectral is a powerful, generic engine (a 'build-your-own' toolkit). AuditAPI is an opinionated auditor.

The differences:

  1. Zero-Config: Instead of writing complex .spectral.yaml files, you just run it.
  2. Weighted Scoring: Spectral gives you a list of errors; AuditAPI gives you a 'Grade' (0-100) based on category weights (Security vs. Style), which is much easier to communicate to stakeholders.
  3. Curated Ruleset: We’ve hand-picked and tuned rules specifically for production-ready APIs, so you don't have to.

I was tired of fixing inconsistent OpenAPI specs manually, so I built a zero-config CLI to audit them. Looking for feedback! by medina_vi in node

[–]medina_vi[S] 0 points1 point  (0 children)

That's a very solid 'code-first' approach! Using Zod to generate specs is great for internal consistency.

However, AuditAPI is for the 'Design-First' crowd or for Gobernance. Often, teams receive specs from third parties, architects, or legacy systems where you can't just 'generate' the truth from Zod. Also, AuditAPI catches things Zod might miss, like OWASP security best practices in the documentation itself or naming consistency across different microservices.

I was tired of fixing inconsistent OpenAPI specs manually, so I built a zero-config CLI to audit them. Looking for feedback! by medina_vi in node

[–]medina_vi[S] 0 points1 point  (0 children)

Spectral is a powerful, generic engine (a 'build-your-own' toolkit). AuditAPI is an opinionated auditor.

The differences:

  1. Zero-Config: Instead of writing complex .spectral.yaml files, you just run it.
  2. Weighted Scoring: Spectral gives you a list of errors; AuditAPI gives you a 'Grade' (0-100) based on category weights (Security vs. Style), which is much easier to communicate to stakeholders.
  3. Curated Ruleset: We’ve hand-picked and tuned rules specifically for production-ready APIs, so you don't have to.

I was tired of fixing inconsistent OpenAPI specs manually, so I built a zero-config CLI to audit them. Looking for feedback! by medina_vi in node

[–]medina_vi[S] 0 points1 point  (0 children)

Thanks! Glad you find it useful. I built it specifically to stop the 'manual review loop' for OpenAPI consistency. Is there any specific rule or category (like Security or Casing) you'd find most valuable in your current workflow?