← Home

@peerbit/any-store

24
Versions
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

marcus.pousette

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:uuid AI (phantom-deps): uuid declared as runtime dep; referenced in config/indirect usage; stable false positive for this package. ai
phantom-deps phantom-dep:@peerbit/time AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic fires on build tooling patterns, not a real import gap. ai
phantom-deps phantom-dep:@peerbit/crypto AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@peerbit/logger AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. ai
phantom-deps phantom-dep:@peerbit/build-assets AI (phantom-deps): Same-org monorepo build tooling dep; stable false positive for this package. ai

Versions (showing 24 of 24)

Version Deps Published
2.2.13 10 / 2
2.2.12 10 / 2
2.2.11 10 / 2
2.2.10 10 / 2
2.2.9 10 / 2
2.2.8 10 / 2
2.2.5 10 / 2
2.2.1 10 / 2
2.1.16 10 / 2
2.1.14 7 / 1
2.1.13 7 / 1
2.1.12 7 / 1
2.1.11 7 / 1
2.1.10 7 / 1
2.1.9 7 / 1
2.1.8 7 / 1
2.1.7 7 / 1
2.1.6 7 / 1
2.1.5 7 / 1
2.1.4 7 / 1
2.1.3 7 / 1
2.1.2 7 / 1
2.1.1 7 / 1
2.1.0 7 / 1

v2.2.13

1 finding
LOW No provenance attestation provenance

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

v2.2.12

1 finding
LOW No provenance attestation provenance

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

v2.2.11

1 finding
LOW No provenance attestation provenance

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

v2.2.10

1 finding
LOW No provenance attestation provenance

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

v2.1.9

1 finding
LOW No provenance attestation provenance

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

v2.1.8

1 finding
LOW No provenance attestation provenance

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

v2.1.7

1 finding
LOW No provenance attestation provenance

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

v2.1.6

1 finding
LOW No provenance attestation provenance

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

v2.1.5

1 finding
LOW No provenance attestation provenance

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

v2.1.4

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

1 finding
LOW No provenance attestation provenance

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

v2.1.2

1 finding
LOW No provenance attestation provenance

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.