@stackone/hub
StackOne HUB
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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 StackOne package with consistent publishing history; lack of provenance is a process gap, not a security signal. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped @stackone org package; Levenshtein match to 'yup' is coincidental, not a typosquat. | ai | |
| phantom-deps | phantom-dep:@stackone/expressions | AI (phantom-deps): Same-org scoped dep; likely re-exported or bundled rather than directly imported. | ai | |
| phantom-deps | phantom-dep:@tanstack/react-query | AI (phantom-deps): Referenced in config files; consistent with bundled library pattern. | ai | |
| phantom-deps | phantom-dep:use-deep-compare-effect | AI (phantom-deps): Referenced in config files; consistent with bundled library pattern. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 1.10.1 | 4 / 16 | |
| 1.10.0 | 4 / 16 | |
| 1.9.0 | 4 / 16 | |
| 1.8.0 | 4 / 16 | |
| 1.7.1 | 4 / 17 | |
| 1.6.0 | 4 / 17 | |
| 1.5.2 | 4 / 17 | |
| 1.5.1 | 4 / 17 | |
| 1.5.0 | 4 / 17 | |
| 1.4.0 | 4 / 25 | |
| 1.3.3 | 4 / 25 | |
| 1.3.2 | 4 / 25 | |
| 1.3.1 | 4 / 25 | |
| 1.3.0 | 4 / 25 | |
| 1.2.0 | 4 / 25 | |
| 1.1.0 | 4 / 18 | |
| 1.0.2 | 4 / 18 | |
| 1.0.1 | 4 / 18 | |
| 1.0.0 | 4 / 18 | |
| 0.13.2 | 4 / 18 | |
| 0.12.9 | 4 / 18 | |
| 0.12.8 | 4 / 18 | |
| 0.12.7 | 4 / 18 | |
| 0.12.6 | 4 / 18 | |
| 0.12.5 | 4 / 18 | |
| 0.12.4 | 4 / 18 | |
| 0.12.3 | 4 / 18 | |
| 0.12.2 | 4 / 18 | |
| 0.12.1 | 4 / 18 | |
| 0.11.2 | 4 / 18 | |
| 0.11.1 | 4 / 18 | |
| 0.11.0 | 4 / 18 | |
| 0.10.2 | 4 / 18 | |
| 0.10.1 | 4 / 18 | |
| 0.10.0 | 4 / 18 | |
| 0.9.1 | 4 / 18 | |
| 0.9.0 | 4 / 18 | |
| 0.8.0 | 4 / 18 | |
| 0.7.4 | 4 / 18 | |
| 0.7.3 | 4 / 18 | |
| 0.7.2 | 4 / 18 | |
| 0.7.1 | 4 / 18 | |
| 0.6.6 | 4 / 18 | |
| 0.6.5 | 4 / 18 | |
| 0.6.4 | 4 / 18 | |
| 0.6.3 | 4 / 18 | |
| 0.6.2 | 4 / 18 | |
| 0.6.1 | 4 / 18 | |
| 0.6.0 | 4 / 18 | |
| 0.5.2 | 4 / 18 | |
| 0.5.1 | 4 / 18 | |
| 0.5.0 | 4 / 18 |
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.