← Home

acorn-jsx

npm Repository Homepage

Modern, fast React.js JSX parser

21
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

marijnadrianheinerreverser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher changed from rreverser to marijn (acorn author) as part of acornjs org consolidation; legitimate and stable. ai
maintainer-change maintainer-added AI (maintainer-change): adrianheine and marijn are core acornjs maintainers; addition reflects org consolidation. ai

Versions (showing 21 of 21)

Version Deps Published
5.3.2 0 / 1
5.3.1 0 / 1
5.3.0 0 / 1
5.2.0 0 / 1
5.1.0 0 / 1
5.0.2 0 / 1
5.0.1 0 / 1
5.0.0 0 / 1
4.1.1 1 / 2
4.1.0 1 / 2
4.0.1 1 / 2
4.0.0 1 / 2
3.0.1 1 / 2
3.0.0 1 / 2
2.0.1 1 / 2
2.0.0 1 / 2
1.0.3 1 / 2
1.0.2 1 / 2
1.0.1 1 / 2
1.0.0 1 / 2
0.6.1 0 / 0

v5.3.1

1 finding
LOW No provenance attestation provenance

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

v5.3.0

1 finding
LOW No provenance attestation provenance

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

v5.2.0

1 finding
LOW No provenance attestation provenance

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

v5.1.0

2 findings
HIGH Publisher changed: rreverser → marijn (on 2019-10-13) provenance

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

v5.0.2

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

v5.0.0

1 finding
LOW No provenance attestation provenance

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

v4.1.1

1 finding
LOW No provenance attestation provenance

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

v4.1.0

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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