@ionic/utils-fs No license 11 versions

@ionic/utils-fs

npm Repository Homepage

11

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ionicjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Known publisher ionicjs with strong track record; no takeover indicators.	ai	2026/07/21
maintainer-change	maintainer-removed	AI (maintainer-change): Routine maintainer roster change for long-lived Ionic package.	ai	2026/07/21
publish-pattern	dormant-publish	AI (publish-pattern): Old, stable utility package; sparse release cadence is normal, not takeover.	ai	2026/07/21
phantom-deps	phantom-dep:debug	AI (phantom-deps): debug is a declared runtime dependency used for logging; phantom-dep heuristic is a false positive for this package.	ai	2026/04/27
phantom-deps	phantom-dep:@types/fs-extra	AI (phantom-deps): @types/fs-extra is a declared dependency supporting the fs-extra runtime; phantom-dep heuristic is a false positive.	ai	2026/04/27

Versions (showing 11 of 11)

Version	Deps	Published
3.1.7	4 / 9	2023-03-29
3.1.6	4 / 9	2022-06-16
3.1.5	3 / 10	2020-08-28
3.1.4	4 / 12	2020-08-25
3.1.3	4 / 12	2020-05-12
3.1.2	4 / 12	2020-05-06
3.1.1	4 / 12	2020-03-03
3.1.0	4 / 12	2020-02-11
3.0.2	4 / 12	2020-02-10
3.0.1	4 / 12	2020-02-03
3.0.0	4 / 12	2020-01-25

v3.1.6

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: dwieeb → ionicjs (on 2022-06-16, known maintainer) provenance

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2022-06-16, but ionicjs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.5

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: dwieeb → ionicjs (on 2020-08-28, known maintainer) provenance

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2020-08-28, but ionicjs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.4

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: dwieeb → ionicjs (on 2020-08-25, known maintainer) provenance

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2020-08-25, but ionicjs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.3

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

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: ionicjs → dwieeb (on 2020-03-03, known maintainer) provenance

This version was published by a different npm account (dwieeb) than the most recent previously approved version (ionicjs) on 2020-03-03, but dwieeb is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.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.