artillery-plugin-publish-metrics
Publish metrics from your Artillery.io tests to external monitoring & observability systems
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:lightstep-tracer | AI (dependencies): lightstep-tracer is a known OpenTracing SDK; stable long-term dependency of this plugin. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.37.0 | 25 / 3 | |
| 2.36.0 | 25 / 3 | |
| 2.35.0 | 24 / 3 | |
| 2.34.0 | 24 / 3 | |
| 2.33.0 | 24 / 3 | |
| 2.32.0 | 24 / 3 | |
| 2.31.0 | 24 / 3 | |
| 2.30.0 | 24 / 3 | |
| 2.29.0 | 24 / 3 | |
| 2.28.0 | 25 / 3 |
v2.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.