@textbus/core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tanbo/di | AI (dependencies): Same author namespace (tanbo) as the package; expected internal DI library. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used in Proxy trap pattern for reactive data model; standard framework idiom, not obfuscation. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @textbus/core is a long-established rich-text editor, not a typosquat of cors. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 5.4.8 | 2 / 2 | |
| 5.4.7 | 2 / 2 | |
| 5.4.6 | 2 / 2 | |
| 5.4.5 | 2 / 2 | |
| 5.4.4 | 2 / 2 | |
| 5.4.3 | 2 / 2 | |
| 5.4.2 | 2 / 2 | |
| 5.4.1 | 2 / 2 | |
| 5.4.0 | 2 / 2 | |
| 5.3.4 | 2 / 2 | |
| 5.3.3 | 2 / 2 | |
| 5.3.2 | 2 / 2 | |
| 5.3.1 | 2 / 2 | |
| 5.3.0 | 2 / 2 | |
| 5.2.7 | 2 / 2 | |
| 5.2.6 | 2 / 2 | |
| 5.2.5 | 2 / 2 | |
| 5.2.4 | 2 / 2 | |
| 5.2.3 | 2 / 2 | |
| 5.2.2 | 2 / 2 | |
| 5.2.1 | 2 / 2 | |
| 5.2.0 | 2 / 2 | |
| 5.1.6 | 2 / 5 | |
| 5.1.5 | 2 / 5 | |
| 5.1.4 | 2 / 5 | |
| 5.1.3 | 2 / 5 | |
| 5.1.2 | 2 / 5 | |
| 5.1.1 | 2 / 5 | |
| 5.1.0 | 2 / 5 | |
| 5.0.0 | 2 / 5 | |
| 3.8.5 | 3 / 5 |
v5.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.