@olane/os
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @olane/os is a scoped org package, not a typosquat of qs; name reflects the oLane OS product. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): 2-edit Levenshtein false positive; scoped org package with clear product identity. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): 2-edit Levenshtein false positive; scoped org package with clear product identity. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): 2-edit Levenshtein false positive; scoped org package with clear product identity. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): 2-edit Levenshtein false positive; scoped org package with clear product identity. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): 2-edit Levenshtein false positive; scoped org package with clear product identity. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): 2-edit Levenshtein false positive; scoped org package with clear product identity. | ai |
Versions (showing 51 of 65)
| Version | Deps | Published |
|---|---|---|
| 0.8.18 | 19 / 21 | |
| 0.8.16 | 17 / 20 | |
| 0.8.15 | 17 / 20 | |
| 0.8.14 | 17 / 20 | |
| 0.8.13 | 17 / 20 | |
| 0.8.12 | 17 / 20 | |
| 0.8.11 | 17 / 20 | |
| 0.8.10 | 17 / 20 | |
| 0.8.9 | 17 / 20 | |
| 0.8.8 | 17 / 20 | |
| 0.8.7 | 17 / 20 | |
| 0.8.6 | 17 / 20 | |
| 0.8.5 | 17 / 20 | |
| 0.8.4 | 17 / 20 | |
| 0.8.3 | 17 / 20 | |
| 0.8.2 | 17 / 20 | |
| 0.8.1 | 17 / 20 | |
| 0.8.0 | 17 / 20 | |
| 0.7.62 | 17 / 20 | |
| 0.7.61 | 17 / 20 | |
| 0.7.60 | 17 / 20 | |
| 0.7.59 | 17 / 20 | |
| 0.7.58 | 17 / 20 | |
| 0.7.57 | 17 / 20 | |
| 0.7.56 | 17 / 20 | |
| 0.7.55 | 17 / 20 | |
| 0.7.54 | 17 / 20 | |
| 0.7.53 | 17 / 20 | |
| 0.7.52 | 17 / 20 | |
| 0.7.51 | 17 / 20 | |
| 0.7.50 | 17 / 20 | |
| 0.7.49 | 17 / 20 | |
| 0.7.48 | 17 / 20 | |
| 0.7.47 | 17 / 20 | |
| 0.7.46 | 17 / 20 | |
| 0.7.45 | 17 / 20 | |
| 0.7.44 | 17 / 20 | |
| 0.7.43 | 17 / 20 | |
| 0.7.42 | 17 / 20 | |
| 0.7.41 | 17 / 20 | |
| 0.7.40 | 17 / 20 | |
| 0.7.39 | 17 / 20 | |
| 0.7.38 | 17 / 20 | |
| 0.7.37 | 17 / 20 | |
| 0.7.36 | 17 / 20 | |
| 0.7.35 | 17 / 20 | |
| 0.7.34 | 17 / 20 | |
| 0.7.33 | 17 / 20 | |
| 0.7.31 | 17 / 20 | |
| 0.7.29 | 17 / 20 | |
| 0.7.28 | 17 / 20 |
v0.8.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.14
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.58
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.55
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.49
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.47
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.44
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.36
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.28
2 findingsPackage name '@olane/os' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.