← Home

@peter.naydenov/data-pool

Data-pool is a data-layer for node apps and single page application

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

Maintainers

dreamgfx

Keywords

datacachestore

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff source-size-tripled AI (source-diff): Size increase is from added rollup dist bundles (UMD/ESM/CJS) and type declarations, not injected code. ai
publish-pattern dormant-publish AI (publish-pattern): No material changes in this release; publisher has clean track record with 13 approved packages. ai
dependencies unvetted-dep:@peter.naydenov/walk AI (dependencies): Same author namespace; consistent with package's own ecosystem. ai
dependencies unvetted-dep:@peter.naydenov/signals AI (dependencies): Same author namespace; consistent with package's own ecosystem. ai

Versions (showing 8 of 8)

Version Deps Published
2.1.3 4 / 7
2.1.2 4 / 7
2.1.1 4 / 7
2.1.0 4 / 7
2.0.3 4 / 3
2.0.2 4 / 3
2.0.1 4 / 3
2.0.0 4 / 3

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

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

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
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.