@trackunit/create-iris-app-workspace
The `create-iris-app-workspace` package is a cli tool extending `create-nx-workspace`.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Trackunit org package with 825 versions; lack of Sigstore attestation is a process gap, not a security signal. | ai | |
| dependencies | unvetted-dep:create-nx-workspace | AI (dependencies): create-nx-workspace is the official Nx workspace scaffolding tool; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency used implicitly by TypeScript-compiled output; stable false positive for this package. | ai |
Versions (showing 100 of 538)
| Version | Deps | Published |
|---|---|---|
| 1.3.130 | 2 / 0 | |
| 1.3.128 | 2 / 0 | |
| 1.3.127 | 2 / 0 | |
| 1.3.126 | 2 / 0 | |
| 1.3.125 | 2 / 0 | |
| 1.3.124 | 2 / 0 | |
| 1.3.122 | 2 / 0 | |
| 1.3.121 | 2 / 0 | |
| 1.3.120 | 2 / 0 | |
| 1.3.119 | 2 / 0 | |
| 1.3.118 | 2 / 0 | |
| 1.3.117 | 2 / 0 | |
| 1.3.116 | 2 / 0 | |
| 1.3.115 | 2 / 0 | |
| 1.3.113 | 2 / 0 | |
| 1.3.112 | 2 / 0 | |
| 1.3.111 | 2 / 0 | |
| 1.3.110 | 2 / 0 | |
| 1.3.109 | 2 / 0 | |
| 1.3.107 | 2 / 0 | |
| 1.3.106 | 2 / 0 | |
| 1.3.105 | 2 / 0 | |
| 1.3.104 | 2 / 0 | |
| 1.3.103 | 2 / 0 | |
| 1.3.101 | 2 / 0 | |
| 1.3.100 | 2 / 0 | |
| 1.3.99 | 2 / 0 | |
| 1.3.98 | 2 / 0 | |
| 1.3.97 | 2 / 0 | |
| 1.3.96 | 2 / 0 | |
| 1.3.92 | 2 / 0 | |
| 1.3.91 | 2 / 0 | |
| 1.3.90 | 2 / 0 | |
| 1.3.89 | 2 / 0 | |
| 1.3.87 | 2 / 0 | |
| 1.3.84 | 2 / 0 | |
| 1.3.83 | 2 / 0 | |
| 1.3.82 | 2 / 0 | |
| 1.3.81 | 2 / 0 | |
| 1.3.80 | 2 / 0 | |
| 1.3.79 | 2 / 0 | |
| 1.3.77 | 2 / 0 | |
| 1.3.76 | 2 / 0 | |
| 1.3.75 | 2 / 0 | |
| 1.3.74 | 2 / 0 | |
| 1.3.73 | 2 / 0 | |
| 1.3.72 | 2 / 0 | |
| 1.3.71 | 2 / 0 | |
| 1.3.69 | 2 / 0 | |
| 1.3.68 | 2 / 0 | |
| 1.3.67 | 2 / 0 | |
| 1.3.65 | 2 / 0 | |
| 1.3.63 | 2 / 0 | |
| 1.3.61 | 2 / 0 | |
| 1.3.60 | 2 / 0 | |
| 1.3.59 | 2 / 0 | |
| 1.3.58 | 2 / 0 | |
| 1.3.57 | 2 / 0 | |
| 1.3.55 | 2 / 0 | |
| 1.3.54 | 2 / 0 | |
| 1.3.53 | 2 / 0 | |
| 1.3.52 | 2 / 0 | |
| 1.3.51 | 2 / 0 | |
| 1.3.50 | 2 / 0 | |
| 1.3.48 | 2 / 0 | |
| 1.3.47 | 2 / 0 | |
| 1.3.46 | 2 / 0 | |
| 1.3.44 | 2 / 0 | |
| 1.3.43 | 2 / 0 | |
| 1.3.41 | 2 / 0 | |
| 1.3.39 | 2 / 0 | |
| 1.3.38 | 2 / 0 | |
| 1.3.37 | 2 / 0 | |
| 1.3.36 | 2 / 0 | |
| 1.3.35 | 2 / 0 | |
| 1.3.34 | 2 / 0 | |
| 1.3.33 | 2 / 0 | |
| 1.3.32 | 2 / 0 | |
| 1.3.30 | 2 / 0 | |
| 1.3.28 | 2 / 0 | |
| 1.3.27 | 2 / 0 | |
| 1.3.23 | 2 / 0 | |
| 1.3.21 | 2 / 0 | |
| 1.3.20 | 2 / 0 | |
| 1.3.18 | 2 / 0 | |
| 1.3.17 | 2 / 0 | |
| 1.3.16 | 2 / 0 | |
| 1.3.14 | 2 / 0 | |
| 1.3.13 | 2 / 0 | |
| 1.3.12 | 2 / 0 | |
| 1.3.11 | 2 / 0 | |
| 1.3.10 | 2 / 0 | |
| 1.3.9 | 2 / 0 | |
| 1.3.6 | 2 / 0 | |
| 1.3.5 | 2 / 0 | |
| 1.3.4 | 2 / 0 | |
| 1.3.2 | 2 / 0 | |
| 1.3.1 | 2 / 0 | |
| 1.2.0 | 2 / 0 | |
| 1.1.1 | 2 / 0 |
v1.3.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.