jsonc-parser
Scanner and parser for JSON with comments.
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.
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 | |
| 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 | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are personal VS Code team accounts replaced by Microsoft org accounts. Legitimate organizational transition. | ai | |
| 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 | |
| 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 |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 0 / 8 | |
| 3.3.0 | 0 / 8 | |
| 3.2.1 | 0 / 8 | |
| 3.2.0 | 0 / 8 | |
| 3.1.0 | 0 / 8 | |
| 3.0.0 | 0 / 8 | |
| 2.3.1 | 0 / 8 | |
| 2.3.0 | 0 / 8 | |
| 2.2.1 | 0 / 6 | |
| 2.2.0 | 0 / 6 | |
| 2.1.1 | 0 / 6 | |
| 2.1.0 | 0 / 6 | |
| 2.0.3 | 0 / 6 | |
| 2.0.2 | 0 / 6 | |
| 2.0.1 | 0 / 6 | |
| 2.0.0 | 0 / 6 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 4 | |
| 0.4.2 | 1 / 4 | |
| 0.4.1 | 1 / 4 | |
| 0.4.0 | 1 / 4 | |
| 0.3.1 | 1 / 4 | |
| 0.3.0 | 1 / 4 | |
| 0.2.3 | 1 / 2 | |
| 0.2.2 | 1 / 2 | |
| 0.2.1 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.3 | 1 / 2 | |
| 0.1.2 | 1 / 2 | |
| 0.1.1 | 1 / 2 | |
| 0.1.0 | 1 / 2 | |
| 0.0.3 | 1 / 2 | |
| 0.0.2 | 1 / 2 | |
| 0.0.1 | 1 / 2 | |
| 4.0.0-next.1 | 0 / 6 |
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.