← Home

@alicloud/gpdb20160503

npm
21
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jacksontianfengmk2pagecaoaliyunsdkteamconsole-fe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@alicloud/openapi-core AI (dependencies): Same Alibaba Cloud org scope; consistent with this SDK's dependency pattern across versions. ai
bogus-package bogus-package AI (bogus-package): Auto-generated Alibaba Cloud SDK package; missing repo/keywords/readme is a stable pattern across this entire SDK family. ai
phantom-deps phantom-dep:@alicloud/credentials AI (phantom-deps): @alicloud/credentials is a declared runtime dep in the same org scope; phantom-dep heuristic is a false positive here. ai

Versions (showing 21 of 21)

Version Deps Published
3.11.0 3 / 5
3.10.0 3 / 5
3.9.0 3 / 5
3.8.0 3 / 5
3.7.0 3 / 5
3.6.0 3 / 5
3.5.0 3 / 5
3.4.1 3 / 5
3.4.0 3 / 5
3.3.0 3 / 5
3.2.2 3 / 5
3.2.1 3 / 5
3.2.0 3 / 5
3.1.0 3 / 5
3.0.3 3 / 5
3.0.2 3 / 5
3.0.1 3 / 5
3.0.0 3 / 5
2.12.1 3 / 5
2.12.0 3 / 5
2.11.0 3 / 5

v3.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.12.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.