@superblocksteam/sdk
Superblocks JS SDK
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:prettier | AI (phantom-deps): Prettier is a tooling/config dependency, not a runtime import; stable false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard Buffer.from(data, 'base64') for file contents; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-node | AI (phantom-deps): OpenTelemetry SDK loaded via config/instrumentation, not direct import. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): OpenTelemetry peer dep loaded by SDK at runtime. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-proposal-decorators | AI (phantom-deps): Babel plugin loaded by convention via config. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/semantic-conventions | AI (phantom-deps): OpenTelemetry peer dep loaded by SDK. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-logs-otlp-http | AI (phantom-deps): OpenTelemetry exporter loaded via SDK config. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-http | AI (phantom-deps): OpenTelemetry exporter loaded via SDK config. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/context-async-hooks | AI (phantom-deps): OpenTelemetry context manager loaded by SDK config. | ai | |
| dependencies | unvetted-dep:@superblocksteam/util | AI (dependencies): Internal sibling package from the same org/publisher; consistent pattern across all versions of this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.0.124 | 41 / 18 | |
| 2.0.123 | 41 / 18 | |
| 2.0.122 | 41 / 18 | |
| 2.0.121 | 41 / 18 | |
| 2.0.120 | 41 / 18 | |
| 2.0.119 | 41 / 18 | |
| 2.0.116 | 41 / 18 | |
| 2.0.108 | 41 / 18 | |
| 2.0.107 | 41 / 18 | |
| 2.0.103 | 41 / 18 | |
| 2.0.101 | 41 / 18 | |
| 2.0.86 | 42 / 19 | |
| 2.0.84 | 42 / 19 | |
| 2.0.83 | 41 / 19 | |
| 2.0.82 | 41 / 19 | |
| 1.14.4 | 5 / 10 | |
| 1.14.3 | 5 / 10 | |
| 1.14.2 | 5 / 10 |
v2.0.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.