@or-sdk/deployer
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 runtime dep; @types/lodash in devDeps satisfies the import pattern. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.7.4 | 2 / 2 | |
| 1.7.3 | 2 / 2 | |
| 1.7.2 | 2 / 2 | |
| 1.7.1 | 2 / 2 | |
| 1.7.0 | 2 / 2 | |
| 1.6.0 | 2 / 2 | |
| 1.5.6 | 2 / 2 | |
| 1.5.5 | 2 / 2 | |
| 1.5.4 | 2 / 2 | |
| 1.5.3 | 2 / 2 | |
| 1.5.2 | 2 / 2 | |
| 1.5.1 | 2 / 2 | |
| 1.5.0 | 2 / 2 | |
| 1.4.5 | 3 / 3 | |
| 1.4.4 | 3 / 3 | |
| 1.4.3 | 3 / 3 | |
| 1.4.2 | 3 / 3 | |
| 1.4.1 | 3 / 3 | |
| 1.4.0 | 3 / 3 | |
| 1.3.12 | 3 / 3 | |
| 1.3.11 | 3 / 3 | |
| 1.3.10 | 3 / 3 | |
| 1.3.9 | 3 / 3 | |
| 1.3.8 | 3 / 3 | |
| 1.3.7 | 3 / 3 | |
| 1.3.6 | 3 / 3 | |
| 1.3.5 | 3 / 3 | |
| 1.3.4 | 3 / 3 | |
| 1.3.3 | 3 / 3 | |
| 1.3.2 | 3 / 3 |
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.