← Home

@apify/datastructures

npm Repository Homepage
7
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mtrunkatjancurnpetrpatekmnmkngjaroslavhejlekdrobnikjmetalwarrior665fnesvedab4nanjanbucharapify-service-account

Keywords

apify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Org service-account migration, stable over 930 days, no malicious behavior. ai
maintainer-change maintainer-removed AI (maintainer-change): Prior individual maintainer replaced by org account; consistent with legitimate transfer. ai
provenance publisher-changed-stale AI (provenance): Long-stable publisher change, analyzer itself notes this is inconsistent with takeover. ai

Versions (showing 7 of 7)

Version Deps Published
2.0.6 0 / 0
2.0.5 0 / 0
2.0.4 0 / 0
2.0.3 0 / 0
2.0.2 0 / 0
2.0.1 0 / 0
2.0.0 0 / 0

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

v2.0.2

2 findings
MEDIUM Publisher changed: mnmkng → apify-service-account (on 2024-01-15, unremoved on npm for 918d) provenance

This version was published by a different npm account (apify-service-account) than the most recent previously approved version (mnmkng) on 2024-01-15. It has since remained available on npm for 918 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.1

2 findings
MEDIUM Publisher changed: mnmkng → apify-service-account (on 2024-01-03, unremoved on npm for 930d) provenance

This version was published by a different npm account (apify-service-account) than the most recent previously approved version (mnmkng) on 2024-01-03. It has since remained available on npm for 930 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.