prompt MIT 38 versions

prompt

npm Repository Homepage

A beautiful command-line prompt for node.js

38

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

fedor.indutnyjcrugzzindexzerobradleymeckcaub

Keywords

promptcommand-linecustomizevalidation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): caub is an established npm publisher (38 approved packages, active since 2019) taking over a mature Nodejitsu package; transition appears legitimate with no malicious indicators.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers bradleymeck and caub are established npm users; addition is consistent with a legitimate community handoff of this Nodejitsu-era package.	ai	2026/04/24

Versions (showing 38 of 38)

Version	Deps	Published
1.3.0	5 / 2	2022-04-11
1.2.2	5 / 2	2022-02-17
1.2.1	5 / 2	2022-01-10
1.2.0	5 / 2	2021-08-25
1.1.0	5 / 1	2020-12-21
1.0.0	6 / 1	2016-02-10
0.3.0	5 / 1	2016-02-07
0.2.14	5 / 1	2014-09-15
0.2.13	5 / 1	2014-05-25
0.2.12	5 / 1	2013-12-09
0.2.11	5 / 1	2013-07-02
0.2.10	5 / 1	2013-07-02
0.2.9	5 / 1	2012-12-19
0.2.8	5 / 1	2012-10-21
0.2.7	5 / 1	2012-08-30
0.2.6	5 / 1	2012-08-12
0.2.5	5 / 1	2012-08-12
0.2.4	5 / 1	2012-08-02
0.2.3	5 / 1	2012-07-27
0.2.2	5 / 1	2012-07-08
0.2.1	5 / 1	2012-06-16
0.2.0	5 / 1	2012-06-16
0.1.12	4 / 1	2012-01-04
0.1.11	4 / 1	2011-12-05
0.1.10	4 / 0	2011-10-25
0.1.9	4 / 0	2011-09-26
0.1.8	4 / 0	2011-09-12
0.1.7	4 / 0	2011-08-22
0.1.5	4 / 0	2011-08-10
0.1.4	4 / 0	2011-08-09
0.1.3	4 / 0	2011-06-29
0.1.2	3 / 0	2011-06-22
0.1.1	3 / 0	2011-06-08
0.1.0	3 / 0	2011-05-30
0.0.4	0 / 0	2011-05-12
0.0.3	0 / 0	2011-03-18
0.0.2	0 / 0	2011-03-18
0.0.1	0 / 0	2011-03-18

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.0

2 findings

HIGH Publisher changed: indexzero → caub (on 2020-12-21) provenance

This version was published by a different npm account than previous versions on 2020-12-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

2 findings

HIGH Publisher changed: jcrugzz → indexzero (on 2016-02-10) provenance

This version was published by a different npm account than previous versions on 2016-02-10. This could indicate a legitimate maintainer transition or an account compromise.

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

1 finding

LOW No provenance attestation provenance

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

v0.2.13

1 finding

LOW No provenance attestation provenance

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

v0.2.12

1 finding

LOW No provenance attestation provenance

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

v0.2.11

1 finding

LOW No provenance attestation provenance

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

v0.2.10

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: avianflu → jcrugzz (on 2013-07-02) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2013-07-02. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.9

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jesusabdullah → avianflu (on 2012-12-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2012-12-19. This could indicate a legitimate maintainer transition or an account compromise.

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.12

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.