@pi-r/oci
Oracle (OCI) cloud functions for E-mc.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:aws-sdk | AI (phantom-deps): aws-sdk is explicitly declared as a runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai | |
| provenance | no-provenance | AI (provenance): Established package with consistent publishing history; lack of Sigstore attestation is not a disqualifier here. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): OCI stands for Oracle Cloud Infrastructure; no relation to 'joi'. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@e-mc/module | AI (phantom-deps): Declared dep used via config/indirect reference in this ecosystem pattern; stable false positive. | ai |
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.12.3 | 7 / 0 | |
| 0.12.2 | 7 / 0 | |
| 0.12.1 | 7 / 0 | |
| 0.12.0 | 7 / 0 | |
| 0.11.3 | 7 / 0 | |
| 0.11.2 | 7 / 0 | |
| 0.11.1 | 7 / 0 | |
| 0.11.0 | 7 / 0 | |
| 0.10.5 | 7 / 0 | |
| 0.10.4 | 7 / 0 | |
| 0.10.3 | 7 / 0 | |
| 0.10.2 | 7 / 0 | |
| 0.10.1 | 7 / 0 | |
| 0.10.0 | 7 / 0 | |
| 0.9.6 | 7 / 0 | |
| 0.9.5 | 7 / 0 | |
| 0.9.4 | 7 / 0 | |
| 0.9.3 | 7 / 0 | |
| 0.9.2 | 7 / 0 | |
| 0.9.1 | 7 / 0 | |
| 0.9.0 | 7 / 0 | |
| 0.8.6 | 7 / 0 | |
| 0.8.5 | 7 / 0 | |
| 0.8.4 | 7 / 0 | |
| 0.8.3 | 7 / 0 | |
| 0.8.2 | 7 / 0 | |
| 0.8.1 | 7 / 0 | |
| 0.8.0 | 7 / 0 | |
| 0.7.7 | 7 / 0 | |
| 0.7.6 | 7 / 0 | |
| 0.7.5 | 7 / 0 | |
| 0.7.4 | 7 / 0 | |
| 0.7.3 | 7 / 0 | |
| 0.7.2 | 7 / 0 | |
| 0.7.1 | 7 / 0 | |
| 0.7.0 | 7 / 0 | |
| 0.6.11 | 7 / 0 | |
| 0.6.10 | 7 / 0 | |
| 0.6.9 | 7 / 0 | |
| 0.6.8 | 7 / 0 | |
| 0.6.7 | 7 / 0 | |
| 0.6.6 | 7 / 0 | |
| 0.6.5 | 7 / 0 | |
| 0.6.3 | 7 / 0 | |
| 0.6.2 | 7 / 0 | |
| 0.6.1 | 7 / 0 | |
| 0.6.0 | 7 / 0 | |
| 0.5.7 | 6 / 0 | |
| 0.5.6 | 6 / 0 | |
| 0.5.5 | 6 / 0 | |
| 0.5.4 | 6 / 0 | |
| 0.5.3 | 6 / 0 | |
| 0.5.2 | 6 / 0 | |
| 0.5.1 | 6 / 0 | |
| 0.5.0 | 6 / 0 | |
| 0.4.0 | 6 / 0 | |
| 0.3.8 | 6 / 0 | |
| 0.3.7 | 6 / 0 | |
| 0.3.6 | 6 / 0 | |
| 0.3.5 | 6 / 0 | |
| 0.3.4 | 6 / 0 | |
| 0.3.3 | 6 / 0 | |
| 0.3.2 | 6 / 0 | |
| 0.3.0 | 6 / 0 | |
| 0.2.14 | 6 / 0 | |
| 0.2.13 | 6 / 0 | |
| 0.2.12 | 6 / 0 | |
| 0.2.11 | 6 / 0 | |
| 0.2.10 | 6 / 0 | |
| 0.2.9 | 6 / 0 | |
| 0.2.8 | 6 / 0 | |
| 0.2.2 | 6 / 0 | |
| 0.2.1 | 6 / 0 | |
| 0.2.0 | 6 / 0 | |
| 0.1.0 | 6 / 0 | |
| 0.0.1 | 6 / 0 |
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.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.
v0.6.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.
v0.6.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.
v0.6.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.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.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.
v0.5.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.
v0.5.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.
v0.5.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.
v0.4.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.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.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.
v0.3.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.
v0.3.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.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.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.
v0.2.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.
v0.2.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.
v0.1.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.
v0.0.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.