@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.11.9 | 26 / 0 | |
| 1.11.8 | 26 / 0 | |
| 1.11.7 | 26 / 0 | |
| 1.11.6 | 26 / 0 | |
| 1.11.0 | 26 / 0 | |
| 1.10.28 | 26 / 0 | |
| 1.10.27 | 26 / 0 | |
| 1.10.25 | 26 / 0 | |
| 1.10.24 | 26 / 0 | |
| 1.10.20 | 26 / 0 | |
| 1.10.18 | 26 / 0 | |
| 1.10.17 | 26 / 0 | |
| 1.10.16 | 26 / 0 | |
| 1.10.15 | 26 / 0 | |
| 1.10.14 | 26 / 0 | |
| 1.10.13 | 26 / 0 | |
| 1.10.12 | 26 / 0 | |
| 1.10.11 | 26 / 0 | |
| 1.10.10 | 26 / 0 | |
| 1.10.6 | 26 / 0 | |
| 1.10.5 | 26 / 0 | |
| 1.10.4 | 26 / 0 | |
| 1.10.3 | 26 / 0 | |
| 1.10.1 | 26 / 0 | |
| 1.10.0 | 26 / 0 | |
| 1.9.23 | 26 / 0 | |
| 1.9.22 | 26 / 0 | |
| 1.9.21 | 26 / 0 | |
| 1.9.20 | 26 / 0 | |
| 1.9.16 | 26 / 0 | |
| 1.9.15 | 26 / 0 | |
| 1.9.13 | 26 / 0 | |
| 1.9.12 | 26 / 0 | |
| 1.9.10 | 26 / 0 | |
| 1.9.9 | 26 / 0 | |
| 1.9.7 | 26 / 0 | |
| 1.9.6 | 26 / 0 | |
| 1.9.4 | 26 / 0 | |
| 1.9.3 | 26 / 0 | |
| 1.9.2 | 26 / 0 | |
| 1.9.1 | 26 / 0 | |
| 1.9.0 | 26 / 0 | |
| 1.8.1 | 26 / 0 | |
| 1.8.0 | 26 / 0 | |
| 1.7.134 | 26 / 0 | |
| 1.7.133 | 26 / 0 | |
| 1.7.130 | 26 / 0 | |
| 1.7.127 | 26 / 0 | |
| 1.7.126 | 26 / 0 | |
| 1.7.124 | 26 / 0 | |
| 1.7.121 | 26 / 0 | |
| 1.7.118 | 26 / 0 | |
| 1.7.117 | 26 / 0 | |
| 1.7.114 | 26 / 0 | |
| 1.7.112 | 26 / 0 | |
| 1.7.111 | 26 / 0 | |
| 1.7.104 | 26 / 0 | |
| 1.7.102 | 26 / 0 | |
| 1.7.101 | 26 / 0 | |
| 1.7.100 | 26 / 0 | |
| 1.7.98 | 26 / 0 | |
| 1.7.96 | 26 / 0 | |
| 1.7.94 | 26 / 0 | |
| 1.7.92 | 26 / 0 | |
| 1.7.90 | 26 / 0 | |
| 1.7.88 | 26 / 0 | |
| 1.7.87 | 26 / 0 | |
| 1.7.86 | 26 / 0 | |
| 1.7.85 | 26 / 0 | |
| 1.7.83 | 26 / 0 | |
| 1.7.82 | 26 / 0 | |
| 1.7.81 | 26 / 0 | |
| 1.7.80 | 26 / 0 | |
| 1.7.78 | 28 / 0 | |
| 1.7.77 | 28 / 0 | |
| 1.7.72 | 28 / 0 | |
| 1.7.71 | 28 / 0 | |
| 1.7.70 | 28 / 0 | |
| 1.7.67 | 28 / 0 | |
| 1.7.65 | 28 / 0 | |
| 1.7.60 | 28 / 0 | |
| 1.7.59 | 28 / 0 | |
| 1.7.58 | 28 / 0 | |
| 1.7.57 | 28 / 0 | |
| 1.7.55 | 28 / 0 | |
| 1.7.54 | 28 / 0 | |
| 1.7.53 | 28 / 0 | |
| 1.7.52 | 28 / 0 | |
| 1.7.50 | 28 / 0 | |
| 1.7.49 | 28 / 0 | |
| 1.7.48 | 28 / 0 | |
| 1.7.47 | 28 / 0 | |
| 1.7.46 | 28 / 0 | |
| 1.7.45 | 28 / 0 | |
| 1.7.43 | 28 / 0 | |
| 1.7.42 | 28 / 0 | |
| 1.7.41 | 28 / 0 | |
| 1.7.40 | 28 / 0 | |
| 1.7.38 | 28 / 0 | |
| 1.7.37 | 28 / 0 |
v1.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.134
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.133
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.127
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.126
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.124
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.121
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.118
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.