jetifier MIT 22 versions

jetifier

npm Repository Homepage

jetifier from Android Studio, in npm package format

22

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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.

Maintainers

mattoakesm4tt72rozpierogmikehardy

Keywords

nodereactreact-nativejetifierjetifier-standaloneandroidx

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Historical transition (2019) from original creator m4tt72 to primary maintainer mikehardy, who is listed as author in package.json with matching GitHub repo. Stable for 6+ years with 173 approved packages.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): Jetifier is a CLI build tool that uses fork() to parallelize file transformation work. child_process usage is architecturally expected and not malicious.	ai	2026/04/23

Versions (showing 22 of 22)

Version	Deps	Published
2.0.0	0 / 1	2021-05-05
1.6.7	0 / 1	2021-05-03
1.6.6	0 / 1	2020-06-11
1.6.5	0 / 1	2019-11-28
1.6.4	0 / 1	2019-08-11
1.6.3	0 / 1	2019-07-13
1.6.2	0 / 1	2019-07-10
1.6.1	0 / 1	2019-07-02
1.6.0	0 / 1	2019-06-30
1.5.1	0 / 1	2019-06-26
1.5.0	0 / 1	2019-06-25
1.4.3	0 / 1	2019-06-23
1.4.2	0 / 1	2019-06-22
1.4.1	0 / 1	2019-06-22
1.4.0	0 / 1	2019-06-20
1.3.2	0 / 1	2019-06-20
1.3.1	0 / 1	2019-06-20
1.3.0	0 / 1	2019-06-20
1.2.0	0 / 1	2019-06-20
1.1.0	0 / 1	2019-06-20
1.0.1	0 / 1	2019-06-18
1.0.0	0 / 1	2019-06-18

v2.0.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: mikehardy.

LOW No provenance attestation provenance

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

v1.6.7

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: mikehardy.

LOW No provenance attestation provenance

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

v1.6.6

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: mikehardy.

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.1

2 findings

HIGH Publisher changed: m4tt72 → mikehardy (on 2019-06-26) provenance

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

v1.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: mikehardy → m4tt72 (on 2019-06-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2019-06-25. This could indicate a legitimate maintainer transition or an account compromise.

v1.4.3

1 finding

LOW No provenance attestation provenance

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

v1.4.2

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.2

1 finding

LOW No provenance attestation provenance

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

v1.3.1

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.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.