← Home

@instana/azure-container-services

Instana tracing and monitoring for Node.js based Azure Container Services

28
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

instana_tracersaryamohanankirrg001abhilash.sivan

Keywords

distributed-tracingazureapp-servicecontainer-servicecaasinstanamemorymetricsmonitoringopentracingperformancetracing

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): aryamohanan is a named contributor with IBM email; consistent with internal IBM/Instana maintainer rotation. ai
provenance no-provenance AI (provenance): Instana monorepo packages consistently lack Sigstore provenance; stable false positive for this package family. ai

Versions (showing 28 of 28)

Version Deps Published
6.5.0 2 / 0
6.4.0 2 / 0
6.3.0 2 / 0
6.2.2 2 / 0
6.2.1 2 / 0
6.2.0 2 / 0
6.1.1 2 / 0
6.1.0 2 / 0
6.0.0 2 / 0
5.5.0 2 / 0
5.4.3 2 / 0
5.4.2 2 / 0
5.4.1 2 / 0
5.4.0 2 / 0
5.3.0 2 / 0
5.2.3 2 / 0
5.2.2 2 / 0
5.2.1 2 / 0
5.2.0 2 / 0
5.1.0 2 / 0
5.0.2 2 / 0
5.0.1 2 / 0
4.31.0 2 / 0
4.30.1 2 / 0
4.30.0 2 / 0
4.29.0 2 / 0
4.28.0 2 / 0
4.27.1 2 / 0

v6.5.0

1 finding
INFO No provenance attestation provenance

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

v6.4.0

1 finding
INFO No provenance attestation provenance

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

v6.3.0

1 finding
INFO No provenance attestation provenance

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

v6.2.2

1 finding
INFO No provenance attestation provenance

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

v6.2.1

1 finding
INFO No provenance attestation provenance

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