jsonc-parser — Greenflagged

Scanner and parser for JSON with comments.

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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.

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher changed from personal MS dev account (aeschli) to Microsoft bot account (vscode-bot) — a documented org-wide transition for VS Code ecosystem packages. Stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are Microsoft organizational accounts (vscode-bot, microsoft1es, etc.), consistent with VS Code team consolidating under org accounts. Not a hostile takeover.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers are personal VS Code team accounts replaced by Microsoft org accounts. Legitimate organizational transition.	ai	2026/04/24
provenance	missing-githead	AI (provenance): Missing gitHead is consistent with the switch to a bot-driven CI/CD publish pipeline. No other provenance anomalies present.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Established Microsoft package published by vscode-bot with 780 approved releases; lack of Sigstore attestation is a process gap, not a security indicator for this package.	ai	2026/04/24

Versions (showing 36 of 36)

Show 1 prerelease

Version	Deps	Published
3.3.1	0 / 8	2024-06-24
3.3.0	0 / 8	2024-06-24
3.2.1	0 / 8	2024-01-22
3.2.0	0 / 8	2022-08-30
3.1.0	0 / 8	2022-07-11
3.0.0	0 / 8	2020-11-13
2.3.1	0 / 8	2020-09-16
2.3.0	0 / 8	2020-07-03
2.2.1	0 / 6	2020-02-21
2.2.0	0 / 6	2019-10-25
2.1.1	0 / 6	2019-08-21
2.1.0	0 / 6	2019-03-29
2.0.3	0 / 6	2019-02-04
2.0.2	0 / 6	2018-08-27
2.0.1	0 / 6	2018-06-25
2.0.0	0 / 6	2018-04-12
1.0.3	0 / 5	2018-03-07
1.0.2	0 / 5	2018-03-05
1.0.1	0 / 5	2018-02-06
1.0.0	0 / 4	2017-05-10
0.4.2	1 / 4	2017-05-05
0.4.1	1 / 4	2017-04-04
0.4.0	1 / 4	2017-02-23
0.3.1	1 / 4	2017-01-26
0.3.0	1 / 4	2017-01-17
0.2.3	1 / 2	2016-06-25
0.2.2	1 / 2	2016-06-14
0.2.1	1 / 2	2016-05-18
0.2.0	1 / 2	2016-04-20
0.1.3	1 / 2	2016-05-15
0.1.2	1 / 2	2016-04-19
0.1.1	1 / 2	2016-04-19
0.1.0	1 / 2	2016-04-19
0.0.3	1 / 2	2016-04-19
0.0.2	1 / 2	2016-04-19
0.0.1	1 / 2	2016-04-18

v3.3.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.

LOW No provenance attestation provenance

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

v3.2.1

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: vscode-bot.

HIGH Publisher changed: aeschli → vscode-bot (on 2024-01-22) provenance

This version was published by a different npm account than previous versions on 2024-01-22. This could indicate a legitimate maintainer transition or an account compromise.