Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Native application entry points for .NET, Python, Java and Dockerfile

Aperta
  • Qualcosa non va?
#161 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp, dockerfile, go, java, kubernetes, python
Ambito
cli, testing, tooling

Direzione di ricerca

Start with the existing Java probe at pkg/intentmap/java.go:35 and review the acceptance criteria for all six missing entry-point types. Use representative inputs to verify detection, then add corresponding interface expectations to tests/map_corpus/golden_expectations.json. Done means each supported type emits project, source path/span, source identity, detector/rule version, and evidence basis.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement follow-up

Release scope update (1.1.0)

The committed launch-declaration slice is tracked by #184. This parent remains open for the broader source entry-point work. It is not a commitment to implement every detector in 1.1.0.

Native application entry points for .NET, Python, Java and Dockerfile

Background

Issue #23 was scoped at 1.0 to cover declared entry points with source evidence. On main, Go main packages, Spring Boot application classes, gRPC service declarations, CLI binaries from Cargo/npm/Go cmd/, and declared ports are detected. Six entry-point types promised in the 1.0-scope comment are not detected.

What 1.0 ships

  • Go main packages as cli_binary interface nodes.
  • Spring Boot application classes (pkg/intentmap/java.go).
  • Cargo binary targets and npm bin fields.
  • gRPC service and operation declarations.
  • Golden corpus interfaces: precision 1.00, recall 0.979 (46 TP, 0 FP, 1 FN).

Remaining work (acceptance criteria from #23)

The following entry-point types were promised in the 1.0-scope comment and are undelivered. An audit of the binary on representative inputs confirmed none produce output:

  • .NET OutputType=Exe projects: No interface node is emitted for a csproj with <OutputType>Exe</OutputType>.
  • C# top-level programs: No interface node for a file-scoped implicit Main.
  • Python if __name__ == "__main__" guards: No interface node for Python entry-point guards.
  • Dockerfile ENTRYPOINT/CMD literals: As interface evidence on a container-build deployable (distinct from the deployable node itself).
  • Kubernetes CronJob schedules: As a scheduled-job interface with the cron expression.
  • Java static void main in a Maven project: A probe exists in pkg/intentmap/java.go:35 but produced no output on a minimal Maven project.

Each must attach project, source path/span, source identity, detector/rule version, and evidence basis per #23's acceptance criteria. An HTTP declaration must not establish runtime reachability or a vulnerability.

Links

  • #23 (1.0.0 issue being closed)
  • pkg/intentmap/java.go (existing Java probe)
  • tests/map_corpus/golden_expectations.json (add interface expectations for new types)
Lingua principale
Go
Stelle
0
Fork
0
Merge medio
5h 8m
PR unite (30g)
54

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di war-and-code/dircue

Tutte le issue di war-and-code/dircue

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.