@superblocksteam/library
[Linear homepage](https://linear.app/superblocks/project/code-mode-11e3f2bd8edb/overview)
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:@dnd-kit/core | AI (phantom-deps): Same bundled UI library pattern. | ai | |
| phantom-deps | phantom-dep:tinycolor2 | AI (phantom-deps): Same bundled UI library pattern. | ai | |
| phantom-deps | phantom-dep:downloadjs | AI (phantom-deps): Same bundled UI library pattern. | ai | |
| phantom-deps | phantom-dep:apca-w3 | AI (phantom-deps): Same bundled UI library pattern. | ai | |
| phantom-deps | phantom-dep:json5 | AI (phantom-deps): Same bundled UI library pattern. | ai | |
| phantom-deps | phantom-dep:rfdc | AI (phantom-deps): Same bundled UI library pattern. | ai | |
| phantom-deps | phantom-dep:interweave | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:memoize-one | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-player | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:shallowequal | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:use-debounce | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@popperjs/core | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:fast-deep-equal | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:interweave-autolink | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@react-hook/resize-observer | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:yaml | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:immer | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-svg | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:decimal.js | AI (phantom-deps): Component library re-exports; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@superblocksteam/fast-deep-equal | AI (dependencies): Same-org scoped package from a well-established publisher with 931 approved packages. | ai | |
| dependencies | unvetted-dep:@superblocksteam/iso-currency | AI (dependencies): Same-org scoped package from a well-established publisher with 931 approved packages. | ai | |
| phantom-deps | phantom-dep:@superblocksteam/iso-currency | AI (phantom-deps): Same-org dep; declared and referenced in config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:moment-timezone | AI (phantom-deps): moment-timezone is a declared dep referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:normalize.css | AI (phantom-deps): normalize.css is a CSS dep referenced via sideEffects/config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:hotkeys-js | AI (phantom-deps): hotkeys-js is a declared dep referenced in config files; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:moment | AI (phantom-deps): moment is a declared dep referenced in config/build files; stable false positive for this package. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 2.0.124 | 38 / 31 | |
| 2.0.123 | 38 / 31 | |
| 2.0.122 | 38 / 31 | |
| 2.0.121 | 38 / 31 | |
| 2.0.120 | 38 / 31 | |
| 2.0.119 | 38 / 30 | |
| 2.0.118 | 38 / 30 | |
| 2.0.117 | 38 / 30 | |
| 2.0.116 | 38 / 30 | |
| 2.0.114 | 38 / 30 | |
| 2.0.111 | 38 / 30 | |
| 2.0.108 | 38 / 30 | |
| 2.0.107 | 38 / 30 | |
| 2.0.105 | 37 / 30 | |
| 2.0.104 | 37 / 30 | |
| 2.0.103 | 37 / 30 | |
| 2.0.100 | 37 / 30 | |
| 2.0.99 | 37 / 30 | |
| 2.0.93 | 37 / 31 | |
| 2.0.92 | 37 / 31 | |
| 2.0.90 | 37 / 31 | |
| 2.0.88 | 35 / 31 | |
| 2.0.87 | 35 / 31 | |
| 2.0.86 | 35 / 31 | |
| 2.0.85 | 35 / 31 | |
| 2.0.82 | 35 / 31 | |
| 2.0.80 | 60 / 39 | |
| 2.0.79 | 60 / 40 | |
| 2.0.78 | 60 / 40 | |
| 2.0.77 | 60 / 40 | |
| 2.0.76 | 60 / 39 | |
| 2.0.75 | 60 / 39 | |
| 2.0.74 | 60 / 39 | |
| 2.0.73 | 60 / 39 | |
| 2.0.72 | 60 / 39 | |
| 2.0.71 | 60 / 39 | |
| 2.0.70 | 60 / 39 | |
| 2.0.69 | 59 / 39 | |
| 2.0.68 | 59 / 39 | |
| 2.0.67 | 59 / 39 | |
| 2.0.66 | 59 / 39 | |
| 2.0.65 | 59 / 39 | |
| 2.0.64 | 59 / 39 | |
| 2.0.63 | 59 / 39 | |
| 2.0.62 | 59 / 39 | |
| 2.0.61 | 59 / 39 | |
| 2.0.60 | 59 / 39 | |
| 2.0.59 | 59 / 39 | |
| 2.0.58 | 59 / 39 | |
| 2.0.57 | 59 / 39 | |
| 2.0.56 | 59 / 39 | |
| 2.0.55 | 57 / 37 | |
| 2.0.54 | 57 / 37 | |
| 2.0.53 | 57 / 37 | |
| 2.0.52 | 57 / 37 | |
| 2.0.51 | 57 / 36 | |
| 2.0.50 | 57 / 36 | |
| 2.0.49 | 57 / 36 | |
| 2.0.42 | 57 / 36 | |
| 2.0.41 | 57 / 36 | |
| 2.0.40 | 57 / 36 | |
| 2.0.39 | 57 / 36 | |
| 2.0.38 | 57 / 36 | |
| 2.0.37 | 57 / 36 | |
| 2.0.36 | 57 / 38 | |
| 2.0.35 | 57 / 38 |
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.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.117
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.93
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.90
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.68
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.