@or-sdk/lookup
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package (974 days, 300 versions); metadata gaps are benign given publisher's track record. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.25.0 | 1 / 3 | |
| 1.24.3 | 1 / 3 | |
| 1.24.2 | 1 / 3 | |
| 1.24.1 | 1 / 3 | |
| 1.24.0 | 1 / 3 | |
| 1.23.1 | 1 / 3 | |
| 1.23.0 | 1 / 3 | |
| 1.22.1 | 1 / 3 | |
| 1.22.0 | 1 / 3 | |
| 1.21.1 | 1 / 3 | |
| 1.21.0 | 1 / 4 | |
| 1.20.2 | 1 / 4 | |
| 1.20.1 | 1 / 4 | |
| 1.20.0 | 1 / 4 | |
| 1.19.3 | 1 / 4 | |
| 1.19.2 | 1 / 4 | |
| 1.19.1 | 1 / 4 | |
| 1.19.0 | 1 / 4 | |
| 1.18.1 | 2 / 6 | |
| 1.18.0 | 2 / 6 | |
| 1.17.0 | 2 / 6 | |
| 1.16.3 | 2 / 6 | |
| 1.16.2 | 2 / 6 | |
| 1.16.1 | 2 / 6 | |
| 1.16.0 | 2 / 6 | |
| 1.15.2 | 2 / 6 | |
| 1.15.1 | 2 / 6 | |
| 1.15.0 | 2 / 6 | |
| 1.14.11 | 2 / 6 | |
| 1.14.10 | 2 / 6 | |
| 1.14.9 | 2 / 6 | |
| 1.14.8 | 2 / 6 | |
| 1.14.7 | 2 / 6 | |
| 1.14.6 | 2 / 6 | |
| 1.14.5 | 2 / 6 | |
| 1.14.4 | 2 / 6 | |
| 1.14.3 | 2 / 6 | |
| 1.14.2 | 2 / 6 | |
| 1.14.1 | 2 / 6 | |
| 1.14.0 | 2 / 6 |
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.