snapdragon MIT 33 versions

snapdragon

npm Repository Homepage

Easy-to-use plugin system for creating powerful, fast and versatile parsers and compilers, with built-in source-map support.

33

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

jonschlinkertdoowbdanez

Keywords

lexersnapdragon

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:source-map-resolve	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
phantom-deps	phantom-dep:export-files	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
phantom-deps	phantom-dep:extend-shallow	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
phantom-deps	phantom-dep:urix	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
phantom-deps	phantom-dep:chalk	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
phantom-deps	phantom-dep:minimist	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
phantom-deps	phantom-dep:source-map	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
phantom-deps	phantom-dep:export-dirs	AI (phantom-deps): Legitimate build/utility dependency; phantom-dep detection on indirect usage is a false positive for this package type.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): danez is a listed contributor with strong ecosystem track record; addition is part of a legitimate project transfer.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition from jonschlinkert to danez (listed contributor) in 2018; danez is a well-established publisher.	ai	2026/04/24

Versions (showing 33 of 33)

Version	Deps	Published
0.12.1	11 / 10	2021-04-09
0.12.0	11 / 10	2018-04-18
0.11.5	12 / 10	2018-04-18
0.11.4	11 / 10	2018-04-09
0.11.3	12 / 10	2018-03-21
0.11.2	12 / 10	2018-02-24
0.11.1	12 / 10	2018-02-24
0.11.0	12 / 10	2017-03-12
0.10.1	12 / 10	2017-02-09
0.10.0	12 / 10	2017-02-07
0.9.1	10 / 10	2017-02-02
0.9.0	10 / 10	2017-01-21
0.8.2	8 / 7	2018-03-11
0.8.1	8 / 7	2016-10-10
0.8.0	8 / 7	2016-10-10
0.7.3	7 / 7	2016-10-10
0.7.2	7 / 7	2016-10-08
0.7.1	7 / 7	2016-10-08
0.7.0	7 / 7	2016-09-27
0.6.0	6 / 6	2016-09-09
0.5.0	5 / 6	2016-09-05
0.4.2	7 / 6	2016-04-29
0.4.1	7 / 6	2016-04-26
0.4.0	7 / 6	2016-04-20
0.3.1	9 / 11	2015-12-09
0.3.0	9 / 11	2015-12-09
0.2.3	11 / 7	2015-12-09
0.2.2	11 / 10	2015-09-24
0.2.1	10 / 5	2015-08-31
0.2.0	8 / 2	2015-05-30
0.1.2	8 / 2	2015-05-16
0.1.1	8 / 2	2015-05-11
0.1.0	8 / 2	2015-05-11

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.5

2 findings

HIGH Publisher changed: jonschlinkert → doowb (on 2018-04-18) provenance

This version was published by a different npm account than previous versions on 2018-04-18. 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.

v0.11.4

2 findings

HIGH Publisher changed: jonschlinkert → danez (on 2018-04-09) provenance

This version was published by a different npm account than previous versions on 2018-04-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.

v0.11.3

1 finding

LOW No provenance attestation provenance

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

v0.11.2

1 finding

LOW No provenance attestation provenance

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

v0.11.1

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

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.