← Home

@classapp-tech/prometheus-integration

A class to make integration with Prometheus Aggregator

12
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

sergiodeveloperarturcrsstephanie.classbenicio.samuelsilvasmvsclassapp_edna

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:ts-jest AI (phantom-deps): Used in jest config for TS transform, not direct import. ai
phantom-deps phantom-dep:ts-node AI (phantom-deps): Used via start script, referenced in config. ai
provenance publisher-changed-stale AI (provenance): Stale change, long-lived on npm, not consistent with takeover. ai

Versions (showing 12 of 12)

Version Deps Published
1.4.0 2 / 19
1.3.0 2 / 17
1.2.2 2 / 17
1.2.1 4 / 15
1.2.0 4 / 15
1.1.4 2 / 6
1.1.3 2 / 6
1.1.1 2 / 4
1.1.0 2 / 6
1.0.2 2 / 1
1.0.1 2 / 0
1.0.0 2 / 0

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.2

2 findings
MEDIUM Publisher changed: benicio.samuel → sergiodeveloper (on 2023-02-08, unremoved on npm for 1263d) provenance

This version was published by a different npm account (sergiodeveloper) than the most recent previously approved version (benicio.samuel) on 2023-02-08. It has since remained available on npm for 1263 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.2.1

2 findings
MEDIUM Publisher changed: benicio.samuel → sergiodeveloper (on 2023-02-08, unremoved on npm for 1263d) provenance

This version was published by a different npm account (sergiodeveloper) than the most recent previously approved version (benicio.samuel) on 2023-02-08. It has since remained available on npm for 1263 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.4

1 finding
LOW No provenance attestation provenance

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

v1.1.3

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.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.