oci-workrequests
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:oci-workrequests | AI (phantom-deps): Self-referential dep in package.json is a known OCI SDK artifact; not a real phantom dependency concern. | ai | |
| dependencies | unvetted-dep:oci-workrequests | AI (dependencies): Self-referential dependency is a packaging quirk of the OCI SDK; stable across versions. | ai |
Versions (showing 99 of 99)
| Version | Deps | Published |
|---|---|---|
| 2.137.1 | 2 / 0 | |
| 2.137.0 | 2 / 0 | |
| 2.136.1 | 3 / 0 | |
| 2.136.0 | 3 / 0 | |
| 2.135.1 | 3 / 0 | |
| 2.135.0 | 3 / 0 | |
| 2.134.1 | 3 / 0 | |
| 2.132.0 | 2 / 0 | |
| 2.131.2 | 2 / 0 | |
| 2.131.1 | 2 / 0 | |
| 2.131.0 | 2 / 0 | |
| 2.130.0 | 2 / 0 | |
| 2.129.0 | 2 / 0 | |
| 2.127.0 | 2 / 0 | |
| 2.126.3 | 2 / 0 | |
| 2.126.2 | 2 / 0 | |
| 2.126.1 | 2 / 0 | |
| 2.126.0 | 2 / 0 | |
| 2.125.3 | 2 / 0 | |
| 2.125.2 | 2 / 0 | |
| 2.125.1 | 2 / 0 | |
| 2.125.0 | 2 / 0 | |
| 2.124.0 | 2 / 0 | |
| 2.123.1 | 2 / 0 | |
| 2.123.0 | 2 / 0 | |
| 2.122.2 | 2 / 0 | |
| 2.122.1 | 2 / 0 | |
| 2.122.0 | 2 / 0 | |
| 2.121.1 | 2 / 0 | |
| 2.121.0 | 2 / 0 | |
| 2.120.0 | 2 / 0 | |
| 2.119.1 | 2 / 0 | |
| 2.119.0 | 2 / 0 | |
| 2.118.1 | 2 / 0 | |
| 2.118.0 | 2 / 0 | |
| 2.117.1 | 2 / 0 | |
| 2.117.0 | 2 / 0 | |
| 2.116.2 | 2 / 0 | |
| 2.116.1 | 2 / 0 | |
| 2.116.0 | 2 / 0 | |
| 2.115.0 | 2 / 0 | |
| 2.114.1 | 2 / 0 | |
| 2.114.0 | 2 / 0 | |
| 2.113.0 | 2 / 0 | |
| 2.112.2 | 2 / 0 | |
| 2.112.1 | 2 / 0 | |
| 2.112.0 | 2 / 0 | |
| 2.111.3 | 2 / 0 | |
| 2.111.2 | 2 / 0 | |
| 2.111.1 | 2 / 0 | |
| 2.111.0 | 2 / 0 | |
| 2.110.0 | 2 / 0 | |
| 2.109.1 | 2 / 0 | |
| 2.109.0 | 2 / 0 | |
| 2.108.0 | 2 / 0 | |
| 2.107.3 | 2 / 0 | |
| 2.107.2 | 2 / 0 | |
| 2.107.1 | 2 / 0 | |
| 2.107.0 | 2 / 0 | |
| 2.106.2 | 2 / 0 | |
| 2.106.1 | 2 / 0 | |
| 2.106.0 | 2 / 0 | |
| 2.105.0 | 2 / 0 | |
| 2.104.0 | 2 / 0 | |
| 2.103.0 | 2 / 0 | |
| 2.102.2 | 2 / 0 | |
| 2.102.1 | 2 / 0 | |
| 2.102.0 | 2 / 0 | |
| 2.101.0 | 2 / 0 | |
| 2.100.3 | 2 / 0 | |
| 2.100.2 | 2 / 0 | |
| 2.100.1 | 2 / 0 | |
| 2.100.0 | 2 / 0 | |
| 2.99.0 | 2 / 0 | |
| 2.98.1 | 2 / 0 | |
| 2.98.0 | 2 / 0 | |
| 2.97.1 | 2 / 0 | |
| 2.97.0 | 2 / 0 | |
| 2.96.0 | 2 / 0 | |
| 2.95.2 | 2 / 0 | |
| 2.95.1 | 2 / 0 | |
| 2.95.0 | 2 / 0 | |
| 2.94.0 | 2 / 0 | |
| 2.93.0 | 2 / 0 | |
| 2.92.0 | 2 / 0 | |
| 2.91.1 | 2 / 0 | |
| 2.91.0 | 2 / 0 | |
| 2.89.4 | 2 / 0 | |
| 2.89.3 | 2 / 0 | |
| 2.89.2 | 2 / 0 | |
| 2.89.1 | 2 / 0 | |
| 2.89.0 | 2 / 0 | |
| 2.88.2 | 2 / 0 | |
| 2.88.1 | 2 / 0 | |
| 2.88.0 | 2 / 0 | |
| 2.87.0 | 2 / 0 | |
| 2.86.3 | 2 / 0 | |
| 2.86.2 | 2 / 0 | |
| 2.86.1 | 2 / 0 |
v2.137.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.107.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.105.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.104.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.103.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.101.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.