antlr4
JavaScript runtime for ANTLR4
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/antlr4.web.mjs | AI (source-diff): Webpack-minified dist output. | ai | |
| source-diff | obfuscated-file:dist/antlr4.node.cjs | AI (source-diff): Webpack-minified dist output. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Bundled dist/source-map files from build; expected for this package. | ai | |
| source-diff | obfuscated-file:dist/antlr4.node.mjs | AI (source-diff): Webpack-minified dist output; matches build script and terser devDep. | ai | |
| source-diff | obfuscated-file:dist/antlr4.web.cjs | AI (source-diff): Webpack-minified dist output. | ai | |
| source-diff | obfuscated-file:dist/antlr4.web.js | AI (source-diff): Webpack-minified browser bundle; expected build artifact. | ai | |
| source-diff | obfuscated-file:dist/antlr4.node.js | AI (source-diff): Webpack-minified dist output with license banner; expected build artifact. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 4.13.2 | 0 / 18 | |
| 4.13.1 | 0 / 18 | |
| 4.12.0 | 0 / 17 | |
| 4.11.0 | 0 / 10 | |
| 4.10.1 | 0 / 10 | |
| 4.10.0 | 0 / 10 | |
| 4.9.3 | 0 / 16 | |
| 4.9.2 | 0 / 7 | |
| 4.9.1 | 0 / 6 | |
| 4.9.0 | 0 / 5 | |
| 4.8.0 | 0 / 0 | |
| 4.7.2 | 0 / 0 | |
| 4.7.1 | 0 / 0 | |
| 4.7.0 | 0 / 0 | |
| 4.6.0 | 0 / 0 | |
| 4.5.3 | 0 / 0 | |
| 4.5.2 | 0 / 0 |
v4.13.1
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (parrt) than the most recent previously approved version (ericvergnaud) on 2022-04-15, but parrt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (ericvergnaud) than the most recent previously approved version (parrt) on 2021-11-06, but ericvergnaud is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
2 findingsThis version was published by a different npm account (parrt) than the most recent previously approved version (ericvergnaud) on 2017-03-31. It has since remained available on npm for 3399 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.