← Home

@ionic/utils-terminal

npm Repository Homepage
16
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ionicjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Ionic org maintainer reshuffle; publisher matched known maintainer, no behavioral change. ai
maintainer-change maintainer-removed AI (maintainer-change): Routine maintainer list update for established Ionic package. ai
publish-pattern dormant-publish AI (publish-pattern): Stable utility package with no code changes; dormancy expected. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): Known implicit runtime dependency, not a real issue. ai
phantom-deps phantom-dep:@types/slice-ansi AI (phantom-deps): @types/slice-ansi is intentionally listed as a runtime dep (not devDep) in this package — a packaging quirk, not a security issue. Stable false positive for this package. ai
bogus-package bogus-package AI (bogus-package): Ionic CLI monorepo sub-package; short README and no keywords are expected for internal utility packages. Not a spam or low-value package. ai

Versions (showing 16 of 16)

Version Deps Published
2.3.5 9 / 11
2.3.4 9 / 11
2.3.3 9 / 11
2.3.2 8 / 12
2.3.1 8 / 10
2.3.0 7 / 9
2.2.1 2 / 9
2.2.0 2 / 10
2.1.4 2 / 10
2.1.3 2 / 10
2.1.2 2 / 10
2.1.1 2 / 10
2.1.0 2 / 10
2.0.2 2 / 10
2.0.1 2 / 10
2.0.0 2 / 10

v2.3.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 2023-03-29, known maintainer) provenance

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2023-03-29, 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.

v2.3.3

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.

v2.3.2

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-05-09, known maintainer) provenance

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2022-05-09, 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.

v2.3.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: dwieeb → ionicjs (on 2020-09-29, known maintainer) provenance

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2020-09-29, 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.

v2.3.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: dwieeb → ionicjs (on 2020-09-24, known maintainer) provenance

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2020-09-24, 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.

v2.2.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: 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.

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

This version was published by a different npm account (ionicjs) than the most recent previously approved version (dwieeb) on 2020-08-27, 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.

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

v2.1.3

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

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.

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