syntax-error
detect and report syntax errors in source code strings
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is the intentional core mechanism of syntax-error: it uses eval with a 'throw STOP' prefix to detect parse errors without executing code. This is stable and expected for this package. | ai | |
| provenance | publisher-changed | AI (provenance): goto-bus-stop is a well-established publisher (1214 approved packages) who took over maintenance of substack's browserify ecosystem packages. Legitimate transition. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.4.0 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.0 | 1 / 1 | |
| 1.1.6 | 1 / 1 | |
| 1.1.5 | 1 / 1 | |
| 1.1.4 | 1 / 1 | |
| 1.1.3 | 1 / 1 | |
| 1.1.2 | 1 / 1 | |
| 1.1.1 | 1 / 1 |
v1.4.0
2 findingsThis version was published by a different npm account than previous versions on 2018-02-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-01-27. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-05-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.