zeparser
My JavaScript parser
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:tests.js | AI (source-diff): tests.js contains only a static array of parser test cases (input strings + expected token counts). No actual network calls or dynamic code execution present; rule is a false positive for this package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to felixge occurred in 2013; felixge is a well-established npm publisher with 159 approved packages. Legitimate maintainer transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Small utility package with infrequent updates; dormancy is normal for stable, dependency-free packages like this. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package is a ~14-year-old early npm stub for the ZeParser project; sparse metadata is consistent with npm conventions of that era, not spam or malice. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 0 / 0 | |
| 0.0.5 | 0 / 0 | |
| 0.0.4 | 0 / 0 | |
| 0.0.3 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v0.0.7
2 findingsThis version was published by a different npm account than previous versions on 2013-06-19. 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.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package 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 2011-11-17. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.