@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, 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 |
|---|---|---|---|---|
| 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 100 of 474)
| Version | Deps | Published |
|---|---|---|
| 1.18.6 | 20 / 0 | |
| 1.18.5 | 20 / 0 | |
| 1.18.4 | 20 / 0 | |
| 1.18.3 | 20 / 0 | |
| 1.18.2 | 20 / 0 | |
| 1.18.1 | 20 / 0 | |
| 1.18.0 | 20 / 0 | |
| 1.17.5 | 20 / 0 | |
| 1.17.4 | 20 / 0 | |
| 1.17.3 | 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.4 | 20 / 0 | |
| 1.15.3 | 20 / 0 | |
| 1.15.1 | 20 / 0 | |
| 1.15.0 | 20 / 0 | |
| 1.14.12 | 20 / 0 | |
| 1.14.11 | 20 / 0 | |
| 1.14.10 | 20 / 0 | |
| 1.14.9 | 20 / 0 | |
| 1.14.8 | 20 / 0 | |
| 1.14.7 | 20 / 0 | |
| 1.14.5 | 20 / 0 | |
| 1.14.4 | 20 / 0 | |
| 1.14.3 | 20 / 0 | |
| 1.14.2 | 20 / 0 | |
| 1.14.1 | 20 / 0 | |
| 1.13.1 | 20 / 0 | |
| 1.13.0 | 20 / 0 | |
| 1.12.24 | 20 / 0 | |
| 1.12.23 | 20 / 0 | |
| 1.12.22 | 20 / 0 | |
| 1.12.21 | 20 / 0 | |
| 1.12.20 | 20 / 0 | |
| 1.12.19 | 20 / 0 | |
| 1.12.17 | 20 / 0 | |
| 1.12.16 | 20 / 0 | |
| 1.12.14 | 20 / 0 | |
| 1.12.13 | 20 / 0 | |
| 1.12.12 | 20 / 0 | |
| 1.12.11 | 20 / 0 | |
| 1.12.10 | 20 / 0 | |
| 1.12.9 | 20 / 0 | |
| 1.12.7 | 20 / 0 | |
| 1.12.6 | 20 / 0 | |
| 1.12.5 | 20 / 0 | |
| 1.12.4 | 20 / 0 | |
| 1.12.3 | 20 / 0 | |
| 1.12.2 | 20 / 0 | |
| 1.12.1 | 20 / 0 | |
| 1.12.0 | 20 / 0 | |
| 1.11.52 | 20 / 0 | |
| 1.11.51 | 20 / 0 | |
| 1.11.50 | 26 / 0 | |
| 1.11.49 | 26 / 0 | |
| 1.11.48 | 26 / 0 | |
| 1.11.47 | 26 / 0 | |
| 1.11.46 | 26 / 0 | |
| 1.11.45 | 26 / 0 | |
| 1.11.44 | 26 / 0 | |
| 1.11.43 | 26 / 0 | |
| 1.11.42 | 26 / 0 | |
| 1.11.41 | 26 / 0 | |
| 1.11.40 | 26 / 0 | |
| 1.11.39 | 26 / 0 | |
| 1.11.38 | 26 / 0 | |
| 1.11.37 | 26 / 0 | |
| 1.11.36 | 26 / 0 | |
| 1.11.35 | 26 / 0 | |
| 1.11.33 | 26 / 0 | |
| 1.11.32 | 26 / 0 | |
| 1.11.31 | 26 / 0 | |
| 1.11.30 | 26 / 0 | |
| 1.11.29 | 26 / 0 | |
| 1.11.28 | 26 / 0 | |
| 1.11.27 | 26 / 0 | |
| 1.11.26 | 26 / 0 | |
| 1.11.25 | 26 / 0 | |
| 1.11.24 | 26 / 0 | |
| 1.11.23 | 26 / 0 | |
| 1.11.22 | 26 / 0 | |
| 1.11.21 | 26 / 0 | |
| 1.11.20 | 26 / 0 | |
| 1.11.19 | 26 / 0 | |
| 1.11.18 | 26 / 0 | |
| 1.11.17 | 26 / 0 | |
| 1.11.16 | 26 / 0 | |
| 1.11.15 | 26 / 0 | |
| 1.11.14 | 26 / 0 | |
| 1.11.13 | 26 / 0 | |
| 1.11.12 | 26 / 0 | |
| 1.11.11 | 26 / 0 | |
| 1.11.10 | 26 / 0 |
v1.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.