oci-objectstorage
OCI NodeJS client for ObjectStorage
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Oracle OCI SDK does not use Sigstore provenance; stable pattern across all 268 versions. | ai | |
| dependencies | unvetted-dep:oci-workrequests | AI (dependencies): oci-workrequests is a sibling OCI SDK package published on the same release train; stable false positive for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): opossum is a well-established circuit breaker library; addition is consistent with Oracle OCI SDK patterns. | ai | |
| phantom-deps | phantom-dep:oci-workrequests | AI (phantom-deps): OCI SDK sibling dep; declared for transitive use, stable false positive for this package. | ai | |
| license | uncommon-license:UPL-1.0 | AI (license): UPL-1.0 is Oracle's standard open-source license used across all OCI SDK packages. | ai |
Versions (showing 99 of 99)
| Version | Deps | Published |
|---|---|---|
| 2.137.1 | 3 / 0 | |
| 2.137.0 | 3 / 0 | |
| 2.136.1 | 4 / 0 | |
| 2.136.0 | 4 / 0 | |
| 2.135.1 | 4 / 0 | |
| 2.135.0 | 4 / 0 | |
| 2.134.1 | 4 / 0 | |
| 2.132.0 | 3 / 0 | |
| 2.131.2 | 3 / 0 | |
| 2.131.1 | 3 / 0 | |
| 2.131.0 | 3 / 0 | |
| 2.130.0 | 3 / 0 | |
| 2.129.0 | 3 / 0 | |
| 2.127.0 | 3 / 0 | |
| 2.126.3 | 3 / 0 | |
| 2.126.2 | 3 / 0 | |
| 2.126.1 | 3 / 0 | |
| 2.126.0 | 3 / 0 | |
| 2.125.3 | 3 / 0 | |
| 2.125.2 | 3 / 0 | |
| 2.125.1 | 3 / 0 | |
| 2.125.0 | 3 / 0 | |
| 2.124.0 | 3 / 0 | |
| 2.123.1 | 3 / 0 | |
| 2.123.0 | 3 / 0 | |
| 2.122.2 | 3 / 0 | |
| 2.122.1 | 3 / 0 | |
| 2.122.0 | 3 / 0 | |
| 2.121.1 | 3 / 0 | |
| 2.121.0 | 3 / 0 | |
| 2.120.0 | 3 / 0 | |
| 2.119.1 | 3 / 0 | |
| 2.119.0 | 3 / 0 | |
| 2.118.1 | 3 / 0 | |
| 2.118.0 | 3 / 0 | |
| 2.117.1 | 3 / 0 | |
| 2.117.0 | 3 / 0 | |
| 2.116.2 | 3 / 0 | |
| 2.116.1 | 3 / 0 | |
| 2.116.0 | 3 / 0 | |
| 2.115.0 | 3 / 0 | |
| 2.114.1 | 3 / 0 | |
| 2.114.0 | 3 / 0 | |
| 2.113.0 | 3 / 0 | |
| 2.112.2 | 3 / 0 | |
| 2.112.1 | 3 / 0 | |
| 2.112.0 | 3 / 0 | |
| 2.111.3 | 3 / 0 | |
| 2.111.2 | 3 / 0 | |
| 2.111.1 | 3 / 0 | |
| 2.111.0 | 3 / 0 | |
| 2.110.0 | 3 / 0 | |
| 2.109.1 | 3 / 0 | |
| 2.109.0 | 3 / 0 | |
| 2.108.0 | 3 / 0 | |
| 2.107.3 | 3 / 0 | |
| 2.107.2 | 3 / 0 | |
| 2.107.1 | 3 / 0 | |
| 2.107.0 | 3 / 0 | |
| 2.106.2 | 3 / 0 | |
| 2.106.1 | 3 / 0 | |
| 2.106.0 | 3 / 0 | |
| 2.105.0 | 3 / 0 | |
| 2.104.0 | 3 / 0 | |
| 2.103.0 | 3 / 0 | |
| 2.102.2 | 3 / 0 | |
| 2.102.1 | 3 / 0 | |
| 2.102.0 | 3 / 0 | |
| 2.101.0 | 3 / 0 | |
| 2.100.3 | 3 / 0 | |
| 2.100.2 | 3 / 0 | |
| 2.100.1 | 3 / 0 | |
| 2.100.0 | 3 / 0 | |
| 2.99.0 | 3 / 0 | |
| 2.98.1 | 3 / 0 | |
| 2.98.0 | 3 / 0 | |
| 2.97.1 | 3 / 0 | |
| 2.97.0 | 3 / 0 | |
| 2.96.0 | 3 / 0 | |
| 2.95.2 | 3 / 0 | |
| 2.95.1 | 3 / 0 | |
| 2.95.0 | 3 / 0 | |
| 2.94.0 | 3 / 0 | |
| 2.93.0 | 3 / 0 | |
| 2.92.0 | 3 / 0 | |
| 2.91.1 | 3 / 0 | |
| 2.91.0 | 3 / 0 | |
| 2.89.4 | 3 / 0 | |
| 2.89.3 | 3 / 0 | |
| 2.89.2 | 3 / 0 | |
| 2.89.1 | 3 / 0 | |
| 2.89.0 | 3 / 0 | |
| 2.88.2 | 3 / 0 | |
| 2.88.1 | 3 / 0 | |
| 2.88.0 | 3 / 0 | |
| 2.87.0 | 3 / 0 | |
| 2.86.3 | 3 / 0 | |
| 2.86.2 | 3 / 0 | |
| 2.86.1 | 3 / 0 |
v2.137.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.137.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.136.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.107.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.107.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.106.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.105.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.104.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.103.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.99.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.97.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.96.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.95.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.93.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.91.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.89.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.86.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.