@textbus/xnote
A high-performance rich text editor that supports multiplayer online collaboration.
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): mermaid is a well-known diagramming library; addition is consistent with editor feature expansion. | ai | |
| provenance | missing-githead | AI (provenance): Established package with 105 versions and matching GitHub repo; missing gitHead likely reflects a publish environment change, not malicious activity. | ai | |
| provenance | no-provenance | AI (provenance): Long-lived package with no history of provenance; not a security risk for this package. | ai | |
| phantom-deps | phantom-dep:@types/markdown-it | AI (phantom-deps): @types packages are type-only and not directly imported; false positive for this package. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used Markdown parser; its use here is expected for a rich text editor. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 8 / 26 | |
| 1.4.18 | 8 / 26 | |
| 1.4.17 | 8 / 26 | |
| 1.4.16 | 8 / 26 | |
| 1.4.15 | 8 / 26 | |
| 1.4.7 | 8 / 26 | |
| 1.3.1 | 8 / 26 | |
| 1.2.6 | 7 / 26 | |
| 1.2.5 | 7 / 26 | |
| 1.2.3 | 7 / 26 | |
| 1.2.2 | 7 / 26 | |
| 1.2.1 | 7 / 26 | |
| 1.2.0 | 13 / 42 | |
| 1.1.4 | 13 / 42 | |
| 1.1.3 | 13 / 42 | |
| 1.1.1 | 13 / 42 | |
| 1.0.2 | 13 / 42 | |
| 1.0.1 | 13 / 42 | |
| 1.0.0 | 13 / 42 | |
| 0.3.9 | 11 / 42 | |
| 0.3.8 | 11 / 41 | |
| 0.3.7 | 11 / 41 | |
| 0.3.6 | 11 / 41 |
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: textbus.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: textbus.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: textbus.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: textbus.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: textbus.
Package 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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.