← Home

@azure/core-amqp

npm Repository Homepage
11
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

azure-sdkmicrosoft1esmicrosoft-oss-releases

Keywords

azureamqpcloud

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:util AI (phantom-deps): Node/browser polyfill declared for bundling; stable pattern across Azure SDK packages. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): Known implicit TypeScript runtime dep; stable false positive for this package. ai
phantom-deps phantom-dep:buffer AI (phantom-deps): Browser polyfill for bundling; stable pattern across Azure SDK packages. ai
phantom-deps phantom-dep:events AI (phantom-deps): Browser polyfill for bundling; stable pattern across Azure SDK packages. ai
phantom-deps phantom-dep:process AI (phantom-deps): Browser polyfill for bundling; stable pattern across Azure SDK packages. ai

Versions (showing 11 of 11)

Version Deps Published
4.5.0 11 / 19
4.4.2 11 / 20
4.4.1 11 / 15
4.4.0 11 / 15
4.3.6 10 / 15
4.3.5 10 / 15
4.3.4 10 / 15
4.3.3 10 / 15
4.3.2 10 / 18
4.3.1 10 / 18
4.3.0 10 / 18

v4.5.0

1 finding
LOW No provenance attestation provenance

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

v4.3.6

1 finding
LOW No provenance attestation provenance

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

v4.3.5

1 finding
LOW No provenance attestation provenance

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

v4.3.4

1 finding
LOW No provenance attestation provenance

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

v4.3.3

1 finding
LOW No provenance attestation provenance

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

v4.3.2

1 finding
LOW No provenance attestation provenance

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

v4.3.1

1 finding
LOW No provenance attestation provenance

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

v4.3.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.