parsimmon — Greenflagged

A monadic LL(infinity) parser combinator library

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

jneenwavebeem

Keywords

parsingparseparsersparser combinators

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
install-scripts	install-script:install	AI (install-scripts): Early version build pattern: `make commonjs` is a local build step for this parser combinator library. No network access or obfuscation.	ai	2026/04/24
email-domain	unclaimed-email:jjmadkisson at gmail dot com	AI (email-domain): False positive: the email is a gmail.com address with obfuscated 'at'/'dot' notation, not a custom unclaimed domain.	ai	2026/04/24
email-domain	unclaimed-email:jneen at jneen dot net	AI (email-domain): Original author's anti-spam obfuscated email in package.json; npm auth is via publisher account, not this field. Stable for this package.	ai	2026/04/23
provenance	no-provenance	AI (provenance): Established package predating Sigstore provenance; informational only, no security risk.	ai	2026/04/23

Versions (showing 45 of 45)

Version	Deps	Published
1.18.1	0 / 14	2021-12-20
1.18.0	0 / 14	2021-06-19
1.17.0	0 / 14	2021-04-18
1.16.0	0 / 14	2020-08-26
1.15.0	0 / 14	2020-07-27
1.14.0	0 / 14	2020-07-09
1.13.0	0 / 14	2019-07-26
1.12.1	0 / 14	2019-07-08
1.12.0	0 / 9	2018-07-13
1.11.1	0 / 9	2018-06-26
1.11.0	0 / 9	2018-06-23
1.10.0	0 / 9	2018-06-17
1.9.0	0 / 9	2018-06-16
1.8.0	0 / 9	2018-06-05
1.7.3	0 / 9	2018-04-22
1.7.2	0 / 8	2018-04-06
1.7.1	0 / 8	2018-03-22
1.7.0	0 / 8	2018-03-10
1.6.4	0 / 8	2018-01-02
1.6.2	0 / 8	2017-07-09
1.6.1	0 / 8	2017-07-02
1.6.0	0 / 6	2017-06-27
1.5.0	0 / 7	2017-06-27
1.4.0	0 / 7	2017-06-06
1.3.0	0 / 7	2017-05-28
1.2.0	0 / 7	2016-12-23
1.1.0	0 / 7	2016-12-22
1.0.0	0 / 7	2016-11-03
0.9.2	0 / 5	2016-08-07
0.9.1	0 / 5	2016-07-09
0.9.0	0 / 5	2016-07-08
0.8.1	0 / 5	2016-07-01
0.8.0	0 / 5	2016-06-29
0.7.2	0 / 5	2016-06-27
0.7.0	1 / 3	2015-03-14
0.6.0	1 / 3	2015-02-24
0.5.1	1 / 3	2014-06-30
0.5.0	1 / 3	2014-06-15
0.4.0	1 / 3	2014-04-18
0.3.2	1 / 3	2014-04-18
0.3.1	1 / 3	2014-03-12
0.3.0	1 / 3	2014-03-12
0.2.1	1 / 3	2014-03-10
0.2.0	1 / 3	2014-01-29
0.0.5	1 / 2	2013-04-10

v1.18.1

2 findings

HIGH Unclaimed maintainer email domain: jneen at jneen dot net email-domain

Maintainer email 'jneen at jneen dot net' uses domain 'jneen at jneen dot net' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v1.18.0

1 finding

INFO No provenance attestation provenance

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

v1.17.0

1 finding

INFO No provenance attestation provenance

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

v1.16.0

1 finding

INFO No provenance attestation provenance

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

v1.15.0

1 finding

INFO No provenance attestation provenance

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

v1.14.0

1 finding

INFO No provenance attestation provenance

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

v1.13.0

1 finding

INFO No provenance attestation provenance

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

v1.12.1

1 finding

INFO No provenance attestation provenance

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

v1.12.0

1 finding

INFO No provenance attestation provenance

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

v1.11.1

1 finding

INFO No provenance attestation provenance

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

v1.11.0

1 finding

INFO No provenance attestation provenance

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

v1.10.0

1 finding

INFO No provenance attestation provenance

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

v1.9.0

1 finding

INFO No provenance attestation provenance

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

v1.8.0

1 finding

INFO No provenance attestation provenance

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

v1.7.3

1 finding

INFO No provenance attestation provenance

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

v1.7.2

1 finding

INFO No provenance attestation provenance

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

v1.7.1

1 finding

INFO No provenance attestation provenance

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

v1.7.0

1 finding

INFO No provenance attestation provenance

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

v1.6.4

1 finding

INFO No provenance attestation provenance

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

v1.6.2

1 finding

INFO No provenance attestation provenance

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

v1.6.1

1 finding

INFO No provenance attestation provenance

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

v1.6.0

1 finding

INFO No provenance attestation provenance

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

v1.5.0

1 finding

INFO No provenance attestation provenance

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

v1.4.0

1 finding

INFO No provenance attestation provenance

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

v1.3.0

1 finding

INFO No provenance attestation provenance

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

v1.2.0

1 finding

INFO No provenance attestation provenance

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

v1.1.0

1 finding

INFO No provenance attestation provenance

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

v1.0.0

1 finding

INFO No provenance attestation provenance

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

v0.9.2

1 finding

INFO No provenance attestation provenance

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

v0.9.1

1 finding

INFO No provenance attestation provenance

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

v0.9.0

1 finding

INFO No provenance attestation provenance

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

v0.8.1

1 finding

INFO No provenance attestation provenance

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

v0.8.0

1 finding

INFO No provenance attestation provenance

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

v0.7.2

1 finding

INFO No provenance attestation provenance

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

v0.7.0

1 finding

INFO No provenance attestation provenance

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

v0.6.0

1 finding

INFO No provenance attestation provenance

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

v0.5.1

1 finding

INFO No provenance attestation provenance

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

v0.5.0

1 finding

INFO No provenance attestation provenance

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

v0.4.0

2 findings

HIGH Unclaimed maintainer email domain: jjmadkisson at gmail dot com email-domain

Maintainer email 'jjmadkisson at gmail dot com' uses domain 'jjmadkisson at gmail dot com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

v0.3.2

2 findings

HIGH Unclaimed maintainer email domain: jjmadkisson at gmail dot com email-domain

Maintainer email 'jjmadkisson at gmail dot com' uses domain 'jjmadkisson at gmail dot com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

v0.3.1

2 findings

HIGH Unclaimed maintainer email domain: jjmadkisson at gmail dot com email-domain

Maintainer email 'jjmadkisson at gmail dot com' uses domain 'jjmadkisson at gmail dot com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

v0.3.0

2 findings

HIGH Unclaimed maintainer email domain: jjmadkisson at gmail dot com email-domain

Maintainer email 'jjmadkisson at gmail dot com' uses domain 'jjmadkisson at gmail dot com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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

v0.2.1

1 finding

INFO No provenance attestation provenance

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

v0.2.0

2 findings

HIGH Package has 'install' script install-scripts

Script: make commonjs

INFO No provenance attestation provenance

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

v0.0.5

3 findings

HIGH Package has 'install' script install-scripts

Script: make commonjs

HIGH Unclaimed maintainer email domain: jjmadkisson at gmail dot com email-domain

Maintainer email 'jjmadkisson at gmail dot com' uses domain 'jjmadkisson at gmail dot com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

INFO No provenance attestation provenance

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