@rango-dev/provider-cosmostation MIT 18 versions

@rango-dev/provider-cosmostation

npm

Cosmostation Wallet integration for hub. [Homepage](https://www.cosmostation.io/) | [Docs](https://docs.cosmostation.io/)

18

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

yeager-eren

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Monorepo workspace package; sparse metadata is a consistent pattern across all @rango-dev packages, not a malice indicator.	ai	2026/05/02
npm-metadata	no-description	AI (npm-metadata): Stable pattern across @rango-dev scoped packages; not indicative of spam or malice.	ai	2026/05/02
publish-pattern	dormant-publish	AI (publish-pattern): Large established monorepo with 283 versions; inactivity gap is plausible for a wallet provider package, no code changes detected.	ai	2026/04/30
dependencies	unvetted-dep:@rango-dev/signer-cosmos	AI (dependencies): Internal rango-dev monorepo sibling; consistent pattern across all versions.	ai	2026/04/28
dependencies	unvetted-dep:rango-types	AI (dependencies): Internal rango-dev ecosystem dep; stable sibling package pattern across all versions.	ai	2026/04/28
dependencies	unvetted-dep:@rango-dev/wallets-shared	AI (dependencies): Internal rango-dev monorepo sibling; consistent pattern across all versions.	ai	2026/04/28
dependencies	unvetted-dep:@rango-dev/provider-keplr	AI (dependencies): Internal rango-dev monorepo sibling; consistent pattern across all versions.	ai	2026/04/28
dependencies	unvetted-dep:@rango-dev/signer-evm	AI (dependencies): Internal rango-dev monorepo sibling; consistent pattern across all versions.	ai	2026/04/28
dependencies	unvetted-dep:@rango-dev/wallets-core	AI (dependencies): Internal rango-dev monorepo sibling; consistent pattern across all versions.	ai	2026/04/28

Versions (showing 18 of 18)

Version	Deps	Published
0.60.0	6 / 0	2026-05-31
0.59.1	6 / 0	2026-05-02
0.59.0	6 / 0	2026-04-29
0.58.0	6 / 0	2025-12-30
0.57.0	6 / 0	2025-12-15
0.56.0	5 / 0	2025-12-09
0.55.0	5 / 0	2025-12-02
0.54.1	5 / 0	2025-11-22
0.52.0	5 / 0	2025-10-29
0.51.0	5 / 0	2025-09-29
0.50.0	5 / 0	2025-09-06
0.49.0	5 / 0	2025-08-19
0.48.0	4 / 0	2025-08-05
0.47.0	4 / 0	2025-07-22
0.46.0	4 / 0	2025-07-09
0.45.0	4 / 0	2025-06-09
0.44.1	4 / 0	2025-05-04
0.44.0	4 / 0	2025-04-30

v0.60.0

1 finding

LOW No provenance attestation provenance

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

v0.59.1

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

v0.54.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.52.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.

v0.51.0

1 finding

LOW No provenance attestation provenance

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

v0.50.0

1 finding

LOW No provenance attestation provenance

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

v0.49.0

1 finding

LOW No provenance attestation provenance

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

v0.48.0

1 finding

LOW No provenance attestation provenance

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

v0.47.0

1 finding

LOW No provenance attestation provenance

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

v0.46.0

1 finding

LOW No provenance attestation provenance

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

v0.45.0

1 finding

LOW No provenance attestation provenance

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

v0.44.1

1 finding

LOW No provenance attestation provenance

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

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