@stacksjs/desktop
Native desktop application framework for stx (powered by Craft)
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file-transition:dist/index.js | AI (source-diff): dist/index.js is Bun-bundled ESM ('// @bun' banner, long single line). No _0x arrays, eval/atob, or packer. Bundling, not obfuscation. | ai | |
| dependencies | unvetted-dep:@stacksjs/server | AI (dependencies): Same-org monorepo sibling package, not third-party. | ai | |
| dependencies | unvetted-dep:unified-network | AI (dependencies): Established dep used across stacksjs packages. | ai | |
| dependencies | unvetted-dep:@stacksjs/build | AI (dependencies): Same-org monorepo sibling package, not third-party. | ai | |
| phantom-deps | phantom-dep:unstorage | AI (phantom-deps): Referenced in config, not direct import. | ai | |
| phantom-deps | phantom-dep:@stacksjs/server | AI (phantom-deps): Same-org scope, config-referenced server package. | ai | |
| phantom-deps | phantom-dep:@tauri-apps/api | AI (phantom-deps): Config-referenced tauri tooling, expected for desktop app. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Used via config/build tooling, not direct import; stable pattern for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@stacksjs/build | AI (phantom-deps): Same-org scope, config-referenced build tool. | ai | |
| phantom-deps | phantom-dep:@tauri-apps/cli | AI (phantom-deps): Config-referenced tauri CLI, expected for desktop app. | ai | |
| phantom-deps | phantom-dep:unified-network | AI (phantom-deps): Config-referenced networking dep, not directly imported by design. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): No material changes in this version; established package with trusted publisher history makes dormant-publish a low-risk signal here. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long history; lack of Sigstore provenance is a process gap, not a security indicator. | ai |
Versions (showing 100 of 217)
| Version | Deps | Published |
|---|---|---|
| 0.56.29 | 0 / 1 | |
| 0.56.28 | 0 / 1 | |
| 0.56.27 | 0 / 1 | |
| 0.56.24 | 0 / 1 | |
| 0.56.23 | 0 / 1 | |
| 0.56.21 | 0 / 1 | |
| 0.56.3 | 0 / 1 | |
| 0.53.1 | 0 / 1 | |
| 0.52.10 | 0 / 1 | |
| 0.52.9 | 0 / 1 | |
| 0.52.8 | 0 / 1 | |
| 0.52.7 | 0 / 1 | |
| 0.52.6 | 0 / 1 | |
| 0.52.5 | 0 / 1 | |
| 0.52.4 | 0 / 1 | |
| 0.52.3 | 0 / 1 | |
| 0.52.2 | 0 / 1 | |
| 0.52.1 | 0 / 1 | |
| 0.52.0 | 0 / 1 | |
| 0.51.0 | 0 / 3 | |
| 0.50.0 | 0 / 3 | |
| 0.49.3 | 0 / 3 | |
| 0.49.2 | 0 / 3 | |
| 0.49.1 | 0 / 3 | |
| 0.49.0 | 0 / 3 | |
| 0.48.3 | 0 / 3 | |
| 0.48.2 | 0 / 3 | |
| 0.48.1 | 0 / 3 | |
| 0.47.4 | 0 / 3 | |
| 0.47.2 | 0 / 3 | |
| 0.47.1 | 0 / 3 | |
| 0.46.4 | 0 / 3 | |
| 0.46.3 | 0 / 3 | |
| 0.46.2 | 0 / 3 | |
| 0.46.1 | 0 / 3 | |
| 0.46.0 | 0 / 3 | |
| 0.45.2 | 0 / 3 | |
| 0.45.1 | 0 / 3 | |
| 0.45.0 | 0 / 3 | |
| 0.44.12 | 0 / 3 | |
| 0.44.11 | 0 / 3 | |
| 0.44.10 | 0 / 3 | |
| 0.44.9 | 0 / 3 | |
| 0.44.8 | 0 / 3 | |
| 0.44.7 | 0 / 3 | |
| 0.44.6 | 0 / 3 | |
| 0.43.1 | 0 / 3 | |
| 0.43.0 | 0 / 3 | |
| 0.42.2 | 0 / 3 | |
| 0.42.1 | 0 / 3 | |
| 0.2.110 | 0 / 0 | |
| 0.2.109 | 0 / 0 | |
| 0.2.108 | 0 / 0 | |
| 0.2.107 | 0 / 0 | |
| 0.2.106 | 0 / 0 | |
| 0.2.105 | 0 / 0 | |
| 0.2.104 | 0 / 0 | |
| 0.2.103 | 0 / 0 | |
| 0.2.102 | 0 / 0 | |
| 0.2.101 | 0 / 0 | |
| 0.2.100 | 0 / 0 | |
| 0.2.99 | 0 / 0 | |
| 0.2.98 | 0 / 0 | |
| 0.2.97 | 0 / 0 | |
| 0.2.96 | 0 / 0 | |
| 0.2.95 | 0 / 0 | |
| 0.2.94 | 0 / 0 | |
| 0.2.93 | 0 / 0 | |
| 0.2.92 | 0 / 0 | |
| 0.2.91 | 0 / 0 | |
| 0.2.90 | 0 / 0 | |
| 0.2.89 | 0 / 0 | |
| 0.2.88 | 0 / 0 | |
| 0.2.84 | 0 / 0 | |
| 0.2.83 | 0 / 0 | |
| 0.2.82 | 0 / 0 | |
| 0.2.81 | 0 / 0 | |
| 0.2.80 | 0 / 0 | |
| 0.2.79 | 0 / 0 | |
| 0.2.78 | 0 / 0 | |
| 0.2.77 | 0 / 0 | |
| 0.2.76 | 0 / 0 | |
| 0.2.75 | 0 / 0 | |
| 0.2.74 | 0 / 0 | |
| 0.2.73 | 0 / 0 | |
| 0.2.72 | 0 / 0 | |
| 0.2.71 | 0 / 0 | |
| 0.2.70 | 0 / 0 | |
| 0.2.69 | 0 / 0 | |
| 0.2.67 | 0 / 0 | |
| 0.2.57 | 0 / 0 | |
| 0.2.55 | 0 / 0 | |
| 0.2.54 | 0 / 0 | |
| 0.2.53 | 0 / 0 | |
| 0.2.46 | 0 / 0 | |
| 0.2.35 | 0 / 0 | |
| 0.2.27 | 0 / 0 | |
| 0.2.26 | 0 / 0 | |
| 0.2.25 | 0 / 0 | |
| 0.2.24 | 0 / 0 |
v0.56.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.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.
v0.56.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.
v0.56.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.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.
v0.56.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.
v0.56.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.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.
v0.52.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.
v0.52.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.
v0.52.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.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.
v0.52.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.
v0.52.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.
v0.52.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.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.
v0.52.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.
v0.52.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.
v0.51.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.
v0.50.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.
v0.49.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.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.
v0.49.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.
v0.49.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.
v0.48.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.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.
v0.48.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.
v0.47.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.
v0.47.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.
v0.47.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.
v0.46.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.
v0.46.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.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.
v0.46.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.
v0.46.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.
v0.45.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.
v0.45.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.
v0.45.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.
v0.44.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.
v0.44.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.
v0.44.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.
v0.44.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.
v0.44.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.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.
v0.43.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.
v0.43.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.
v0.42.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.
v0.42.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.
v0.2.110
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.109
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.108
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.107
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.106
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.105
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.104
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.103
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.102
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.101
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.100
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (chrisbreuer) on 2026-07-26, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.2.99
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (chrisbreuer) on 2026-07-19, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.2.98
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.97
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.96
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.95
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.94
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (chrisbreuer) on 2026-07-15, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.
v0.2.93
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.92
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.91
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.90
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.89
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.88
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.84
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.83
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.82
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.81
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.80
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.78
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.77
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.