@trackunit/iris-app-sdk-rspack
The `@trackunit/iris-app-sdk-rspack` package contains an executor for Rspack bundler used for IrisAppSDK development.
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Used in a build-tool package-version checker; expected pattern for NX executor tooling. | ai | |
| dependencies | unvetted-dep:win-ca | AI (dependencies): win-ca is a legitimate Windows CA certificate utility; appropriate for a cross-platform build SDK. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads a user-supplied manifest path in a build executor — standard build-tool pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Trackunit SDK; sparse README and no keywords are consistent with org-internal tooling, not spam. | ai |
Versions (showing 100 of 545)
| Version | Deps | Published |
|---|---|---|
| 1.3.154 | 13 / 0 | |
| 1.3.153 | 13 / 0 | |
| 1.3.152 | 13 / 0 | |
| 1.3.151 | 13 / 0 | |
| 1.3.145 | 13 / 0 | |
| 1.3.144 | 13 / 0 | |
| 1.3.143 | 13 / 0 | |
| 1.3.140 | 13 / 0 | |
| 1.3.139 | 13 / 0 | |
| 1.3.138 | 13 / 0 | |
| 1.3.137 | 13 / 0 | |
| 1.3.136 | 13 / 0 | |
| 1.3.134 | 13 / 0 | |
| 1.3.133 | 13 / 0 | |
| 1.3.132 | 13 / 0 | |
| 1.3.131 | 13 / 0 | |
| 1.3.129 | 13 / 0 | |
| 1.3.127 | 13 / 0 | |
| 1.3.125 | 13 / 0 | |
| 1.3.124 | 13 / 0 | |
| 1.3.123 | 13 / 0 | |
| 1.3.122 | 13 / 0 | |
| 1.3.120 | 13 / 0 | |
| 1.3.119 | 13 / 0 | |
| 1.3.118 | 13 / 0 | |
| 1.3.116 | 13 / 0 | |
| 1.3.115 | 13 / 0 | |
| 1.3.113 | 13 / 0 | |
| 1.3.112 | 13 / 0 | |
| 1.3.110 | 13 / 0 | |
| 1.3.109 | 13 / 0 | |
| 1.3.107 | 13 / 0 | |
| 1.3.106 | 13 / 0 | |
| 1.3.105 | 13 / 0 | |
| 1.3.104 | 13 / 0 | |
| 1.3.103 | 13 / 0 | |
| 1.3.101 | 13 / 0 | |
| 1.3.100 | 13 / 0 | |
| 1.3.96 | 13 / 0 | |
| 1.3.95 | 13 / 0 | |
| 1.3.94 | 13 / 0 | |
| 1.3.93 | 13 / 0 | |
| 1.3.91 | 13 / 0 | |
| 1.3.88 | 13 / 0 | |
| 1.3.87 | 13 / 0 | |
| 1.3.86 | 13 / 0 | |
| 1.3.85 | 13 / 0 | |
| 1.3.84 | 13 / 0 | |
| 1.3.83 | 13 / 0 | |
| 1.3.82 | 13 / 0 | |
| 1.3.80 | 13 / 0 | |
| 1.3.79 | 13 / 0 | |
| 1.3.78 | 13 / 0 | |
| 1.3.76 | 13 / 0 | |
| 1.3.75 | 13 / 0 | |
| 1.3.74 | 13 / 0 | |
| 1.3.73 | 13 / 0 | |
| 1.3.71 | 13 / 0 | |
| 1.3.70 | 13 / 0 | |
| 1.3.69 | 13 / 0 | |
| 1.3.67 | 13 / 0 | |
| 1.3.65 | 13 / 0 | |
| 1.3.63 | 13 / 0 | |
| 1.3.62 | 13 / 0 | |
| 1.3.61 | 13 / 0 | |
| 1.3.60 | 13 / 0 | |
| 1.3.59 | 13 / 0 | |
| 1.3.57 | 13 / 0 | |
| 1.3.56 | 13 / 0 | |
| 1.3.55 | 13 / 0 | |
| 1.3.54 | 13 / 0 | |
| 1.3.53 | 13 / 0 | |
| 1.3.52 | 13 / 0 | |
| 1.3.50 | 13 / 0 | |
| 1.3.49 | 13 / 0 | |
| 1.3.48 | 13 / 0 | |
| 1.3.46 | 13 / 0 | |
| 1.3.45 | 13 / 0 | |
| 1.3.43 | 13 / 0 | |
| 1.3.40 | 13 / 0 | |
| 1.3.39 | 13 / 0 | |
| 1.3.38 | 13 / 0 | |
| 1.3.37 | 13 / 0 | |
| 1.3.36 | 13 / 0 | |
| 1.3.35 | 13 / 0 | |
| 1.3.34 | 13 / 0 | |
| 1.3.33 | 13 / 0 | |
| 1.3.32 | 13 / 0 | |
| 1.3.30 | 13 / 0 | |
| 1.3.28 | 13 / 0 | |
| 1.3.27 | 13 / 0 | |
| 1.3.23 | 13 / 0 | |
| 1.3.21 | 13 / 0 | |
| 1.3.20 | 13 / 0 | |
| 1.3.18 | 13 / 0 | |
| 1.3.17 | 13 / 0 | |
| 1.3.16 | 13 / 0 | |
| 1.3.14 | 13 / 0 | |
| 1.3.13 | 13 / 0 | |
| 1.3.12 | 13 / 0 |
v1.3.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.