← Home

@rango-dev/provider-tomo

npm
28
Versions
MIT
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

yeager-eren

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): 134-version established package family; long gap likely reflects monorepo release cadence, not takeover. ai
bogus-package bogus-package AI (bogus-package): Part of @rango-dev monorepo; sparse metadata is a consistent pattern across all their packages, not a spam indicator. ai
npm-metadata no-description AI (npm-metadata): Consistent with @rango-dev monorepo publishing style; not a security concern. ai

Versions (showing 28 of 28)

Version Deps Published
0.27.0 4 / 0
0.26.1 4 / 0
0.26.0 4 / 0
0.25.0 4 / 0
0.24.0 4 / 0
0.23.0 4 / 0
0.22.0 4 / 0
0.21.1 4 / 0
0.19.0 4 / 0
0.18.0 4 / 0
0.17.0 4 / 0
0.16.0 4 / 0
0.15.0 3 / 0
0.14.0 3 / 0
0.13.0 3 / 0
0.12.0 3 / 0
0.11.1 3 / 0
0.11.0 3 / 0
0.10.0 3 / 0
0.9.0 3 / 0
0.8.0 3 / 0
0.7.0 3 / 0
0.6.0 3 / 0
0.5.0 3 / 0
0.4.0 3 / 0
0.3.0 3 / 0
0.2.1 3 / 0
0.2.0 3 / 0

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.1

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.

v0.2.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.