@redstone-finance/utils MIT 21 versions

@redstone-finance/utils

npm

This package is destined to use internally. We gather here functionalities which are used across many data-packages. This has two big advantages:

21

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

redstone-finance

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:coverage/prettify.js	AI (source-diff): Known third-party google-code-prettify lib in coverage output, not malicious obfuscation.	ai	2026/07/13
bogus-package	bogus-package	AI (bogus-package): Internal utils package in a monorepo; sparse metadata is normal.	ai	2026/07/13
semgrep	semgrep:base64-decode	AI (semgrep): Plain base64 decode utility function; no obfuscation or payload hiding present.	ai	2026/04/29
phantom-deps	phantom-dep:@types/lodash	AI (phantom-deps): @types/lodash is a type-only package legitimately listed as a runtime dep; stable false positive for this package.	ai	2026/04/29

Versions (showing 21 of 21)

Version	Deps	Published
0.9.0	7 / 2	2025-08-11
0.8.0	7 / 0	2025-02-19
0.7.5	7 / 0	2025-02-05
0.7.4	5 / 0	2025-02-04
0.7.3	5 / 0	2024-12-11
0.7.2	5 / 0	2024-11-29
0.7.1	5 / 0	2024-11-26
0.7.0	5 / 0	2024-11-26
0.6.2	5 / 0	2024-09-16
0.6.1	5 / 0	2024-07-24
0.6.0	5 / 0	2024-07-18
0.5.4	5 / 0	2024-06-06
0.5.3	5 / 0	2024-06-06
0.5.2	5 / 0	2024-06-06
0.5.1	5 / 0	2024-05-16
0.5.0	5 / 0	2024-05-10
0.4.0	4 / 0	2024-04-03
0.3.6	4 / 0	2023-11-07
0.3.5	4 / 0	2023-11-06
0.3.4	4 / 0	2023-10-12
0.3.3	4 / 0	2023-10-05

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.5

1 finding

LOW No provenance attestation provenance

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

v0.7.4

1 finding

LOW No provenance attestation provenance

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

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

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

1 finding

LOW No provenance attestation provenance

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

v0.6.1

2 findings

HIGH New obfuscated file: coverage/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.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.5.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.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.6

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

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.3.3

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.