@orama/orama
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:ramda | AI (typosquat): @orama/orama is an established search engine package, not a typosquat of ramda; scoped name is unrelated. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.1.18 | 0 / 22 | |
| 3.1.17 | 0 / 21 | |
| 3.1.16 | 0 / 21 | |
| 3.1.15 | 0 / 21 | |
| 3.1.14 | 0 / 21 | |
| 3.1.13 | 0 / 21 | |
| 3.1.12 | 0 / 21 | |
| 3.1.11 | 0 / 21 | |
| 3.1.10 | 0 / 21 | |
| 3.1.9 | 0 / 21 | |
| 3.1.7 | 0 / 21 | |
| 3.1.6 | 0 / 21 | |
| 3.1.5 | 0 / 21 | |
| 3.1.4 | 0 / 21 | |
| 3.1.3 | 0 / 21 | |
| 3.1.2 | 0 / 21 | |
| 3.1.1 | 0 / 21 | |
| 3.1.0 | 0 / 21 | |
| 3.0.8 | 0 / 21 | |
| 3.0.7 | 0 / 21 | |
| 3.0.6 | 0 / 21 | |
| 3.0.5 | 0 / 21 | |
| 3.0.4 | 0 / 21 | |
| 3.0.3 | 0 / 21 | |
| 3.0.2 | 0 / 21 | |
| 3.0.1 | 0 / 21 | |
| 3.0.0 | 0 / 21 |
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.