@trackunit/iris-app-build-utilities
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used in build utility (checkPackageVersion.js) alongside pacote/semver for version checking; consistent with legitimate build tooling across all versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 15 / 0 | |
| 2.0.6 | 15 / 0 | |
| 2.0.5 | 15 / 0 | |
| 2.0.4 | 15 / 0 | |
| 2.0.3 | 15 / 0 | |
| 2.0.2 | 15 / 0 | |
| 1.16.2 | 15 / 0 | |
| 1.16.1 | 15 / 0 | |
| 1.16.0 | 15 / 0 | |
| 1.15.20 | 14 / 0 | |
| 1.13.18 | 14 / 0 |
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
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.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.