@super-repo/tui MIT 11 versions

@super-repo/tui

npm

Terminal UI for staging and shipping cross-repo migrations across the super stack

11

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

interc0der

Keywords

tuiinkmonorepogitsuper

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:uuid	AI (typosquat): Scoped TUI package; name similarity to uuid is coincidental substring match, not impersonation.	ai	2026/05/10
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped TUI package; name similarity to joi is coincidental substring match, not impersonation.	ai	2026/05/10
typosquat	typosquat.levenshtein:yup	AI (typosquat): Scoped TUI package; name similarity to yup is coincidental substring match, not impersonation.	ai	2026/05/10

Versions (showing 11 of 11)

Version	Deps	Published
0.4.0	6 / 5	2026-05-10
0.3.0	6 / 5	2026-05-10
0.2.2	6 / 5	2026-05-09
0.2.1	6 / 5	2026-05-09
0.2.0	6 / 5	2026-05-06
0.1.0	6 / 5	2026-05-05
0.0.7	6 / 5	2026-05-04
0.0.6	6 / 5	2026-05-04
0.0.5	6 / 5	2026-05-02
0.0.4	6 / 5	2026-05-02
0.0.3	6 / 5	2026-05-02

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.