ora
Elegant terminal spinner
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:koa | AI (typosquat): ora is a well-established terminal spinner package by sindresorhus, not a typosquat of koa. The name similarity is purely coincidental. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): ora is a well-established terminal spinner package by sindresorhus, not a typosquat of cors. The name similarity is purely coincidental. | ai | |
| provenance | no-provenance | AI (provenance): sindresorhus packages historically do not use Sigstore provenance; not a risk signal for this trusted publisher. | ai |
Versions (showing 56 of 56)
| Version | Deps | Published |
|---|---|---|
| 9.4.0 | 8 / 5 | |
| 9.3.0 | 8 / 6 | |
| 9.2.0 | 8 / 6 | |
| 9.1.0 | 8 / 6 | |
| 9.0.0 | 9 / 6 | |
| 8.2.0 | 9 / 6 | |
| 8.1.1 | 9 / 6 | |
| 8.1.0 | 9 / 6 | |
| 8.0.1 | 9 / 6 | |
| 8.0.0 | 9 / 6 | |
| 7.0.1 | 9 / 6 | |
| 7.0.0 | 8 / 6 | |
| 6.3.1 | 9 / 6 | |
| 6.3.0 | 9 / 6 | |
| 6.2.0 | 9 / 6 | |
| 6.1.2 | 9 / 6 | |
| 6.1.1 | 9 / 6 | |
| 6.1.0 | 9 / 6 | |
| 6.0.1 | 9 / 6 | |
| 6.0.0 | 9 / 6 | |
| 5.4.1 | 9 / 5 | |
| 5.4.0 | 9 / 5 | |
| 5.3.0 | 8 / 5 | |
| 5.2.0 | 8 / 5 | |
| 5.1.0 | 8 / 5 | |
| 5.0.0 | 8 / 5 | |
| 4.1.1 | 8 / 5 | |
| 4.1.0 | 8 / 5 | |
| 4.0.5 | 8 / 5 | |
| 4.0.4 | 8 / 5 | |
| 4.0.3 | 8 / 5 | |
| 4.0.2 | 7 / 5 | |
| 4.0.1 | 7 / 5 | |
| 4.0.0 | 7 / 5 | |
| 3.4.0 | 6 / 5 | |
| 3.3.1 | 6 / 5 | |
| 3.3.0 | 6 / 5 | |
| 3.2.0 | 6 / 5 | |
| 3.1.0 | 6 / 3 | |
| 3.0.0 | 6 / 3 | |
| 2.1.0 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.4.0 | 4 / 4 | |
| 1.3.0 | 4 / 4 | |
| 1.2.0 | 4 / 4 | |
| 1.1.0 | 4 / 3 | |
| 1.0.0 | 4 / 3 | |
| 0.4.1 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.0 | 4 / 3 | |
| 0.2.3 | 4 / 3 | |
| 0.2.2 | 4 / 3 | |
| 0.2.1 | 4 / 3 | |
| 0.2.0 | 4 / 3 | |
| 0.1.1 | 4 / 3 | |
| 0.1.0 | 4 / 3 |
v7.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.