@stackone/connect-sdk
This package contains the StackOne Connect SDK that can be used to easily connect to the StackOne platform and also to multiple different API providers.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@stackone/core | AI (phantom-deps): Monorepo re-export pattern; @stackone/* deps are stable across versions. | ai | |
| phantom-deps | phantom-dep:@stackone/defender | AI (phantom-deps): Monorepo re-export pattern; @stackone/* deps are stable across versions. | ai | |
| phantom-deps | phantom-dep:@stackone/expressions | AI (phantom-deps): Monorepo re-export pattern; @stackone/* deps are stable across versions. | ai | |
| phantom-deps | phantom-dep:@stackone/logger | AI (phantom-deps): Monorepo re-export pattern; @stackone/* deps are stable across versions. | ai | |
| phantom-deps | phantom-dep:@stackone/olap | AI (phantom-deps): Monorepo re-export pattern; @stackone/* deps are stable across versions. | ai | |
| phantom-deps | phantom-dep:@stackone/transport | AI (phantom-deps): Monorepo re-export pattern; @stackone/* deps are stable across versions. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Used indirectly via build/config tooling; stable across versions. | ai | |
| phantom-deps | phantom-dep:path-to-regexp | AI (phantom-deps): Used indirectly via build/config tooling; stable across versions. | ai |
Versions (showing 100 of 114)
| Version | Deps | Published |
|---|---|---|
| 2.91.0 | 9 / 0 | |
| 2.90.0 | 9 / 0 | |
| 2.89.0 | 9 / 0 | |
| 2.88.0 | 9 / 0 | |
| 2.87.1 | 9 / 0 | |
| 2.87.0 | 9 / 0 | |
| 2.86.0 | 9 / 0 | |
| 2.85.0 | 9 / 0 | |
| 2.84.0 | 9 / 0 | |
| 2.83.0 | 9 / 0 | |
| 2.82.0 | 9 / 0 | |
| 2.81.0 | 9 / 0 | |
| 2.80.0 | 9 / 0 | |
| 2.79.0 | 9 / 0 | |
| 2.78.0 | 9 / 0 | |
| 2.77.2 | 9 / 0 | |
| 2.76.0 | 9 / 0 | |
| 2.75.0 | 9 / 0 | |
| 2.74.0 | 9 / 0 | |
| 2.73.0 | 9 / 0 | |
| 2.71.1 | 9 / 0 | |
| 2.71.0 | 9 / 0 | |
| 2.70.0 | 9 / 0 | |
| 2.69.0 | 9 / 0 | |
| 2.68.0 | 9 / 0 | |
| 2.67.2 | 9 / 0 | |
| 2.67.1 | 9 / 0 | |
| 2.67.0 | 9 / 0 | |
| 2.66.0 | 9 / 0 | |
| 2.65.0 | 9 / 0 | |
| 2.64.0 | 9 / 0 | |
| 2.63.0 | 9 / 0 | |
| 2.62.0 | 9 / 0 | |
| 2.61.0 | 9 / 0 | |
| 2.60.0 | 9 / 0 | |
| 2.59.0 | 9 / 0 | |
| 2.58.0 | 9 / 0 | |
| 2.57.0 | 9 / 0 | |
| 2.56.0 | 9 / 0 | |
| 2.55.2 | 9 / 0 | |
| 2.55.1 | 9 / 0 | |
| 2.55.0 | 9 / 0 | |
| 2.54.0 | 9 / 0 | |
| 2.53.0 | 9 / 0 | |
| 2.52.0 | 9 / 0 | |
| 2.51.0 | 9 / 0 | |
| 2.50.1 | 9 / 0 | |
| 2.50.0 | 9 / 0 | |
| 2.49.0 | 9 / 0 | |
| 2.48.0 | 9 / 0 | |
| 2.47.0 | 9 / 0 | |
| 2.46.0 | 9 / 0 | |
| 2.45.0 | 9 / 0 | |
| 2.44.2 | 9 / 0 | |
| 2.44.1 | 9 / 0 | |
| 2.44.0 | 9 / 0 | |
| 2.43.0 | 9 / 0 | |
| 2.42.0 | 9 / 0 | |
| 2.41.0 | 9 / 0 | |
| 2.40.0 | 9 / 0 | |
| 2.39.1 | 9 / 0 | |
| 2.39.0 | 9 / 0 | |
| 2.38.0 | 9 / 0 | |
| 2.37.0 | 9 / 0 | |
| 2.36.0 | 9 / 0 | |
| 2.35.0 | 9 / 0 | |
| 2.34.4 | 9 / 0 | |
| 2.34.3 | 9 / 0 | |
| 2.34.2 | 9 / 0 | |
| 2.34.1 | 9 / 0 | |
| 2.34.0 | 9 / 0 | |
| 2.33.0 | 9 / 0 | |
| 2.32.0 | 8 / 0 | |
| 2.31.0 | 8 / 0 | |
| 2.30.0 | 8 / 0 | |
| 2.29.0 | 8 / 0 | |
| 2.28.0 | 8 / 0 | |
| 2.27.0 | 8 / 0 | |
| 2.26.0 | 8 / 0 | |
| 2.25.0 | 8 / 0 | |
| 2.24.0 | 8 / 0 | |
| 2.23.0 | 8 / 0 | |
| 2.22.1 | 8 / 0 | |
| 2.22.0 | 8 / 0 | |
| 2.21.1 | 8 / 0 | |
| 2.21.0 | 8 / 0 | |
| 2.20.1 | 8 / 0 | |
| 2.20.0 | 8 / 0 | |
| 2.19.1 | 8 / 0 | |
| 2.19.0 | 8 / 0 | |
| 2.18.0 | 8 / 0 | |
| 2.17.0 | 8 / 0 | |
| 2.16.0 | 8 / 0 | |
| 2.15.0 | 8 / 0 | |
| 2.14.0 | 8 / 0 | |
| 2.13.0 | 8 / 0 | |
| 2.12.0 | 8 / 0 | |
| 2.11.0 | 8 / 0 | |
| 2.10.0 | 8 / 0 | |
| 2.9.0 | 8 / 0 |
v2.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.74.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.