@ionic/utils-array
Supply chain provenance
Status for the latest visible version.
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
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): Ionic team monorepo maintainer churn; no behavioral change in this version. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer rotation for a long-lived, high-trust package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Ionic utils packages release in bursts tied to CLI releases; benign dormancy pattern. | ai | |
| phantom-deps | phantom-dep:debug | AI (phantom-deps): debug is a declared runtime dependency; phantom-dep heuristic is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.1.6 | 2 / 9 | |
| 2.1.5 | 2 / 9 | |
| 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.1.5
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dwieeb) than the most recent previously approved version (ionicjs) on 2020-05-06, 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.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.