@or-sdk/base
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 declared in dependencies; phantom-dep heuristic is a false positive for this package. | ai |
Versions (showing 51 of 103)
| Version | Deps | Published |
|---|---|---|
| 0.44.3 | 2 / 3 | |
| 0.44.2 | 2 / 3 | |
| 0.44.1 | 2 / 3 | |
| 0.44.0 | 2 / 3 | |
| 0.43.0 | 2 / 3 | |
| 0.42.5 | 2 / 3 | |
| 0.42.4 | 2 / 3 | |
| 0.42.3 | 2 / 4 | |
| 0.42.2 | 2 / 4 | |
| 0.42.1 | 2 / 4 | |
| 0.42.0 | 2 / 4 | |
| 0.41.0 | 3 / 5 | |
| 0.40.0 | 3 / 5 | |
| 0.39.3 | 3 / 5 | |
| 0.39.2 | 3 / 5 | |
| 0.39.1 | 3 / 5 | |
| 0.39.0 | 3 / 5 | |
| 0.38.3 | 3 / 5 | |
| 0.38.2 | 3 / 5 | |
| 0.38.1 | 3 / 5 | |
| 0.38.0 | 3 / 5 | |
| 0.37.0 | 3 / 5 | |
| 0.36.0 | 3 / 5 | |
| 0.35.5 | 3 / 5 | |
| 0.35.4 | 3 / 5 | |
| 0.35.3 | 3 / 5 | |
| 0.35.2 | 3 / 5 | |
| 0.35.1 | 3 / 5 | |
| 0.35.0 | 3 / 5 | |
| 0.34.1 | 3 / 5 | |
| 0.34.0 | 3 / 5 | |
| 0.33.1 | 3 / 5 | |
| 0.33.0 | 3 / 5 | |
| 0.32.0 | 3 / 5 | |
| 0.31.0 | 3 / 5 | |
| 0.30.0 | 3 / 5 | |
| 0.29.2 | 3 / 5 | |
| 0.29.1 | 3 / 4 | |
| 0.29.0 | 3 / 4 | |
| 0.28.3 | 3 / 4 | |
| 0.28.2 | 3 / 4 | |
| 0.28.1 | 3 / 4 | |
| 0.28.0 | 3 / 4 | |
| 0.27.0 | 3 / 4 | |
| 0.26.8 | 3 / 4 | |
| 0.26.7 | 3 / 4 | |
| 0.26.6 | 3 / 4 | |
| 0.26.5 | 3 / 4 | |
| 0.26.4 | 2 / 4 | |
| 0.26.3 | 2 / 4 | |
| 0.26.2 | 2 / 4 |
v0.44.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.