← Home

@trackunit/iris-app-sdk-rspack

The `@trackunit/iris-app-sdk-rspack` package contains an executor for Rspack bundler used for IrisAppSDK development.

100
Versions
SEE LICENSE IN LICENSE.txt
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

sandbankemtandrupkla-trackunitmta-tubch-trackunittu-publisher

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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
2.1.19 10 / 0
2.1.18 10 / 0
2.1.16 10 / 0
2.1.14 10 / 0
2.1.8 10 / 0
2.1.7 10 / 0
2.1.6 10 / 0
2.1.5 10 / 0
2.1.4 10 / 0
2.1.3 10 / 0
2.1.2 10 / 0
2.1.1 10 / 0
2.1.0 10 / 0
2.0.56 10 / 0
2.0.55 10 / 0
2.0.54 10 / 0
2.0.53 10 / 0
2.0.52 10 / 0
2.0.51 10 / 0
2.0.50 10 / 0
2.0.48 10 / 0
2.0.47 10 / 0
2.0.45 10 / 0
2.0.44 10 / 0
2.0.43 10 / 0
2.0.42 10 / 0
2.0.41 10 / 0
2.0.40 10 / 0
2.0.39 10 / 0
2.0.38 10 / 0
2.0.37 10 / 0
2.0.36 10 / 0
2.0.35 10 / 0
2.0.33 10 / 0
2.0.32 10 / 0
2.0.30 10 / 0
2.0.29 10 / 0
2.0.28 10 / 0
2.0.27 10 / 0
2.0.26 10 / 0
2.0.25 10 / 0
2.0.23 10 / 0
2.0.22 10 / 0
2.0.21 10 / 0
2.0.20 10 / 0
2.0.19 10 / 0
2.0.18 10 / 0
2.0.14 10 / 0
2.0.13 10 / 0
2.0.12 10 / 0
2.0.11 10 / 0
2.0.10 10 / 0
2.0.9 10 / 0
2.0.8 10 / 0
2.0.7 10 / 0
2.0.6 10 / 0
2.0.5 10 / 0
2.0.4 10 / 0
2.0.3 10 / 0
2.0.2 10 / 0
2.0.1 10 / 0
2.0.0 10 / 0
1.17.10 10 / 0
1.17.9 10 / 0
1.17.8 10 / 0
1.17.7 10 / 0
1.17.5 10 / 0
1.17.4 10 / 0
1.17.3 10 / 0
1.17.2 10 / 0
1.17.1 10 / 0
1.17.0 10 / 0
1.16.8 10 / 0
1.16.7 10 / 0
1.16.6 10 / 0
1.16.5 10 / 0
1.16.4 10 / 0
1.16.3 10 / 0
1.16.2 10 / 0
1.15.4 10 / 0
1.15.3 10 / 0
1.15.2 10 / 0
1.15.1 10 / 0
1.15.0 10 / 0
1.14.20 10 / 0
1.14.19 10 / 0
1.14.18 10 / 0
1.14.16 10 / 0
1.14.15 10 / 0
1.14.14 10 / 0
1.14.13 10 / 0
1.14.11 10 / 0
1.14.9 10 / 0
1.14.8 10 / 0
1.14.7 10 / 0
1.14.6 10 / 0
1.14.5 10 / 0
1.14.4 10 / 0
1.14.3 10 / 0
1.14.2 10 / 0
Showing 100 of 545 Next page →

v2.1.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.56

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.55

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.52

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.51

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.50

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.48

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.44

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.43

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.42

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.41

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.39

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.38

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.37

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.