← Home

@tinkoff/utils

npm Repository Homepage
21
Versions
—
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

hondasmxmakar_ltinkoffbanktom910dmitry-korolevroulandishivanytsarevashoom3301waterpleameskillmarsibarsizig-greendefenderbasssuper_olegdersizesalexkvak

Keywords

tinkoffutilsramdalodashcurryperformance

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
vendored-integrity tampered-vendored-dep:build AI (vendored-integrity): Only package.json/CHANGELOG differ — routine metadata, not payload. ai
vendored-integrity tampered-vendored-dep:. AI (vendored-integrity): Root package.json diff is expected version metadata. ai
maintainer-change maintainer-added AI (maintainer-change): Stale 2019 transition, long-stable, no malicious behavior since. ai
maintainer-change maintainer-removed AI (maintainer-change): Same stale 2019 transition; no evidence of takeover. ai
provenance publisher-changed-stale AI (provenance): Change is old and stable per analyzer's own note; not indicative of compromise. ai

Versions (showing 21 of 21)

Version Deps Published
2.6.2 0 / 27
2.6.1 0 / 27
2.6.0 0 / 31
2.5.6 0 / 27
2.5.5 0 / 27
2.5.4 0 / 31
2.5.3 0 / 31
2.5.2 0 / 31
2.5.1 0 / 31
2.5.0 0 / 29
2.4.0 0 / 29
2.3.2 0 / 30
2.3.1 0 / 30
2.3.0 0 / 30
2.2.1 0 / 30
2.2.0 0 / 30
2.1.3 0 / 30
2.1.2 0 / 30
2.1.1 0 / 30
2.1.0 0 / 29
2.0.0 0 / 29

v2.6.1

1 finding
LOW No provenance attestation provenance

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

v2.6.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: meskill → marsibarsi (on 2023-07-31, known maintainer) provenance

This version was published by a different npm account (marsibarsi) than the most recent previously approved version (meskill) on 2023-07-31, but marsibarsi is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.5.6

1 finding
LOW No provenance attestation provenance

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

v2.5.5

1 finding
LOW No provenance attestation provenance

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

v2.5.4

3 findings
HIGH Modified vendored dependency: build (2 file(s)) vendored-integrity

The directory `build` byte-matched 364 of 366 file(s) against @tinkoff/[email protected] — a version that passed review and that we hold in storage — which identifies it as a vendored copy of that package. But 2 file(s) inside it differ from that package's bytes at the same path: build/CHANGELOG.md, build/package.json. A vendored library that is a faithful copy except for a handful of altered files is a well-worn supply-chain shape — the surrounding real code lends the tree legitimacy while the altered files carry the payload. These files are NOT exempt from any authorship heuristic; diff them against @tinkoff/[email protected] before greenflagging.

HIGH Modified vendored dependency: . (1 file(s)) vendored-integrity

The directory `.` byte-matched 0 of 0 file(s) against an upstream package — a version that passed review and that we hold in storage — which identifies it as a vendored copy of that package. But 1 file(s) inside it differ from that package's bytes at the same path: package.json. A vendored library that is a faithful copy except for a handful of altered files is a well-worn supply-chain shape — the surrounding real code lends the tree legitimacy while the altered files carry the payload. These files are NOT exempt from any authorship heuristic; diff them against an upstream package before greenflagging.

LOW No provenance attestation provenance

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

v2.5.3

1 finding
LOW No provenance attestation provenance

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

v2.5.2

1 finding
LOW No provenance attestation provenance

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

v2.5.1

1 finding
LOW No provenance attestation provenance

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

v2.5.0

1 finding
LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.1

1 finding
LOW No provenance attestation provenance

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

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.3

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: tom910 → meskill (on 2020-09-10, known maintainer) provenance

This version was published by a different npm account (meskill) than the most recent previously approved version (tom910) on 2020-09-10, but meskill is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.1.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: osorokotyaga → tom910 (on 2019-09-16, known maintainer) provenance

This version was published by a different npm account (tom910) than the most recent previously approved version (osorokotyaga) on 2019-09-16, but tom910 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.1.1

2 findings
MEDIUM Publisher changed: osorokotyaga → meskill (on 2019-09-02, unremoved on npm for 2518d) provenance

This version was published by a different npm account (meskill) than the most recent previously approved version (osorokotyaga) on 2019-09-02. It has since remained available on npm for 2518 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.

v2.1.0

2 findings
MEDIUM Publisher changed: osorokotyaga → meskill (on 2019-08-22, unremoved on npm for 2528d) provenance

This version was published by a different npm account (meskill) than the most recent previously approved version (osorokotyaga) on 2019-08-22. It has since remained available on npm for 2528 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.

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