@trackunit/iris-app
The `@trackunit/iris-app` package is a plugin for [NX by @nrwl](https://nx.dev/). This plugin adds some helpful generators used to set up a Trackunit Iris App project.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@trackunit/react-test-setup | AI (phantom-deps): Internal org dependency; newly added but not directly imported—acceptable for test setup. | ai | |
| phantom-deps | phantom-dep:nx | AI (phantom-deps): Nx is a peer/config dependency for executor packages; stable pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Executor loads user-supplied webpack config files at runtime; stable pattern for this build-tool package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in checkPackageVersion utility; expected for an NX executor tool, not a malware indicator. | ai | |
| dependencies | unvetted-dep:@nx/eslint | AI (dependencies): Well-known Nx monorepo tooling; not a malware risk. | ai | |
| dependencies | unvetted-dep:win-ca | AI (dependencies): win-ca is a known Windows CA certificate utility; stable legitimate dependency for this package. | ai | |
| dependencies | unvetted-dep:@nx/react | AI (dependencies): Well-known Nx monorepo tooling; not a malware risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Trackunit tooling package; link-dump README and empty main are consistent with its role across 1045 versions. | ai | |
| phantom-deps | phantom-dep:@npm/types | AI (phantom-deps): Type-only dependency; not directly imported at runtime is expected for @npm/types. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 20 / 0 | |
| 2.0.6 | 20 / 0 | |
| 2.0.5 | 20 / 0 | |
| 2.0.4 | 20 / 0 | |
| 2.0.3 | 20 / 0 | |
| 2.0.2 | 20 / 0 | |
| 1.21.8 | 20 / 0 | |
| 1.21.6 | 20 / 0 | |
| 1.21.5 | 20 / 0 | |
| 1.21.3 | 20 / 0 | |
| 1.21.2 | 20 / 0 | |
| 1.21.1 | 20 / 0 | |
| 1.21.0 | 20 / 0 | |
| 1.20.7 | 20 / 0 | |
| 1.20.5 | 20 / 0 | |
| 1.20.4 | 20 / 0 | |
| 1.20.3 | 20 / 0 | |
| 1.19.4 | 20 / 0 | |
| 1.19.3 | 20 / 0 | |
| 1.19.2 | 20 / 0 | |
| 1.19.1 | 20 / 0 | |
| 1.19.0 | 20 / 0 | |
| 1.18.22 | 20 / 0 | |
| 1.18.21 | 20 / 0 | |
| 1.18.20 | 20 / 0 | |
| 1.18.19 | 20 / 0 | |
| 1.18.15 | 20 / 0 | |
| 1.18.8 | 20 / 0 | |
| 1.18.4 | 20 / 0 | |
| 1.18.1 | 20 / 0 | |
| 1.18.0 | 20 / 0 | |
| 1.17.5 | 20 / 0 | |
| 1.16.1 | 20 / 0 | |
| 1.16.0 | 20 / 0 | |
| 1.15.11 | 20 / 0 | |
| 1.15.10 | 20 / 0 | |
| 1.15.9 | 20 / 0 | |
| 1.15.8 | 20 / 0 | |
| 1.15.7 | 20 / 0 | |
| 1.15.6 | 20 / 0 | |
| 1.15.5 | 20 / 0 | |
| 1.15.0 | 20 / 0 | |
| 1.14.4 | 20 / 0 | |
| 1.14.1 | 20 / 0 | |
| 1.13.1 | 20 / 0 | |
| 1.12.19 | 20 / 0 | |
| 1.12.13 | 20 / 0 | |
| 1.12.10 | 20 / 0 | |
| 1.12.7 | 20 / 0 | |
| 1.12.5 | 20 / 0 | |
| 1.12.3 | 20 / 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.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.5
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.