@my-react/react-terminal MIT 25 versions

@my-react/react-terminal

npm Repository Homepage

@my-react/react-terminal

25

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

mrwang555

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Likely a CI/publish environment change; no other risk signals present and package has a legitimate repo.	ai	2026/05/27
bogus-package	bogus-package	AI (bogus-package): Sparse metadata is consistent with a monorepo sub-package; not indicative of spam or malware.	ai	2026/05/18
phantom-deps	phantom-dep:slice-ansi	AI (phantom-deps): Declared in dependencies; used indirectly in terminal rendering.	ai	2026/04/29
phantom-deps	phantom-dep:widest-line	AI (phantom-deps): Declared in dependencies; used indirectly in terminal rendering.	ai	2026/04/29
phantom-deps	phantom-dep:cli-truncate	AI (phantom-deps): Declared in dependencies; used indirectly in terminal rendering.	ai	2026/04/29
phantom-deps	phantom-dep:indent-string	AI (phantom-deps): Declared in dependencies; used indirectly in terminal rendering.	ai	2026/04/29

Versions (showing 25 of 25)

Version	Deps	Published
0.0.26	22 / 5	2026-05-25
0.0.25	22 / 5	2026-05-25
0.0.24	22 / 5	2026-05-20
0.0.23	22 / 5	2026-04-27
0.0.21	23 / 4	2026-04-03
0.0.20	23 / 4	2026-04-03
0.0.19	23 / 4	2026-03-17
0.0.18	23 / 4	2026-02-10
0.0.17	23 / 4	2026-02-06
0.0.16	23 / 4	2026-01-08
0.0.15	23 / 4	2025-11-28
0.0.14	22 / 4	2025-10-14
0.0.13	22 / 4	2025-10-09
0.0.12	22 / 4	2025-09-30
0.0.11	22 / 4	2025-08-11
0.0.10	22 / 4	2025-07-28
0.0.9	22 / 4	2025-07-15
0.0.8	22 / 4	2025-07-05
0.0.7	22 / 4	2025-07-03
0.0.6	22 / 4	2025-07-03
0.0.5	22 / 4	2025-06-16
0.0.4	22 / 4	2025-06-16
0.0.3	22 / 4	2025-06-05
0.0.2	22 / 4	2025-05-30
0.0.1	22 / 6	2025-05-20

v0.0.26

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mrwang555.

LOW No provenance attestation provenance

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

v0.0.25

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mrwang555.

LOW No provenance attestation provenance

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

v0.0.24

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mrwang555.

LOW No provenance attestation provenance

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

v0.0.21

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.20

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.19

1 finding

LOW No provenance attestation provenance

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

v0.0.18

1 finding

LOW No provenance attestation provenance

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

v0.0.17

1 finding

LOW No provenance attestation provenance

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

v0.0.16

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.15

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.14

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mrwang555.

LOW No provenance attestation provenance

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

v0.0.13

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mrwang555.

LOW No provenance attestation provenance

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

v0.0.12

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mrwang555.

LOW No provenance attestation provenance

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

v0.0.11

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mrwang555.

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.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.0.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.