← Home

antlr4-c3

npm Repository Homepage

A code completion core implementation for ANTLR4 based parsers

2
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mike.lischke

Keywords

ANTLR4code completionauto completiongrammarparser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): mike-lischke and mike.lischke are the same person (Mike Lischke); same GitHub org, same repo URL, same author field. This is an account rename/migration, not a hostile takeover. ai
provenance publisher-changed AI (provenance): Publisher change from mike-lischke to mike.lischke reflects an npm account rename by the same individual; repo and author metadata are consistent across versions. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer mike.lischke is the same person as mike-lischke (account rename); not a new third party. ai
maintainer-change maintainer-removed AI (maintainer-change): mike-lischke was removed because the account was renamed to mike.lischke; not a hostile removal. ai
publish-pattern new-deps-added AI (publish-pattern): antlr4ng is the well-known successor ANTLR4 TypeScript runtime, replacing antlr4ts; a legitimate and expected dependency for this package. ai
dependencies unvetted-dep:antlr4ts AI (dependencies): antlr4ts is the official TypeScript ANTLR4 runtime; its alpha version tag is expected and stable for this package's use case. ai

Versions (showing 2 of 2)

Version Deps Published
3.4.4 1 / 18
3.0.1 1 / 14

v3.4.4

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (mike-lischke) were replaced by new maintainers (mike.lischke). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: mike-lischke → mike.lischke (on 2025-03-09) provenance

This version was published by a different npm account than previous versions on 2025-03-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.