← Home

corestore

npm Repository Homepage
49
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

mafintosh

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:bare-events AI (phantom-deps): bare-events is used via package.json imports map conditional, not a direct import; stable false positive for this package. ai
provenance publisher-changed AI (provenance): Holepunch org uses GitHub Actions for publishing with SLSA attestation; CI publisher is expected going forward. ai
dependencies unvetted-dep:b4a AI (dependencies): b4a is a standard Holepunch buffer utility used across the ecosystem; stable false positive for this package. ai

Versions (showing 49 of 49)

Version Deps Published
7.11.1 10 / 5
7.11.0 10 / 5
7.10.1 10 / 5
7.10.0 10 / 5
7.9.2 8 / 6
7.9.1 8 / 6
7.9.0 8 / 6
7.8.0 8 / 6
7.7.0 8 / 5
7.6.1 8 / 5
7.6.0 8 / 5
7.5.0 8 / 5
7.4.8 8 / 4
7.4.7 8 / 4
7.4.6 8 / 4
7.4.5 8 / 4
7.4.4 8 / 4
7.4.3 8 / 4
7.4.2 7 / 4
7.4.1 7 / 4
7.4.0 7 / 4
7.3.0 7 / 4
7.2.1 7 / 4
7.2.0 7 / 4
7.1.0 7 / 4
7.0.23 7 / 4
7.0.22 7 / 4
7.0.21 7 / 4
7.0.20 7 / 4
7.0.19 7 / 4
7.0.18 7 / 4
7.0.17 7 / 4
7.0.16 6 / 4
7.0.15 6 / 4
7.0.14 6 / 4
7.0.13 7 / 4
7.0.12 7 / 4
7.0.11 7 / 4
7.0.10 7 / 4
7.0.9 7 / 4
7.0.8 7 / 4
7.0.7 7 / 4
7.0.6 7 / 4
7.0.5 7 / 4
7.0.4 7 / 4
7.0.3 7 / 4
7.0.2 7 / 4
7.0.1 7 / 4
7.0.0 7 / 4

v7.11.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v7.4.1

1 finding
LOW No provenance attestation provenance

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

v7.4.0

1 finding
LOW No provenance attestation provenance

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

v7.3.0

1 finding
LOW No provenance attestation provenance

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

v7.2.1

1 finding
LOW No provenance attestation provenance

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

v7.2.0

1 finding
LOW No provenance attestation provenance

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

v7.1.0

1 finding
LOW No provenance attestation provenance

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

v7.0.23

1 finding
LOW No provenance attestation provenance

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

v7.0.22

1 finding
LOW No provenance attestation provenance

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

v7.0.21

1 finding
LOW No provenance attestation provenance

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

v7.0.20

1 finding
LOW No provenance attestation provenance

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

v7.0.19

1 finding
LOW No provenance attestation provenance

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

v7.0.18

1 finding
LOW No provenance attestation provenance

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

v7.0.17

1 finding
LOW No provenance attestation provenance

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

v7.0.16

1 finding
LOW No provenance attestation provenance

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

v7.0.15

1 finding
LOW No provenance attestation provenance

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

v7.0.14

1 finding
LOW No provenance attestation provenance

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

v7.0.13

1 finding
LOW No provenance attestation provenance

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

v7.0.12

1 finding
LOW No provenance attestation provenance

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

v7.0.11

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: chm-diederichs → mafintosh (on 2025-03-07, known maintainer) provenance

This version was published by a different npm account (mafintosh) than the most recent previously approved version (chm-diederichs) on 2025-03-07, but mafintosh 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.

v7.0.10

1 finding
LOW No provenance attestation provenance

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

v7.0.9

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: mafintosh → chm-diederichs (on 2025-03-07) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-07. This could indicate a legitimate maintainer transition or an account compromise.

v7.0.8

1 finding
LOW No provenance attestation provenance

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

v7.0.7

1 finding
LOW No provenance attestation provenance

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

v7.0.6

1 finding
LOW No provenance attestation provenance

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

v7.0.5

1 finding
LOW No provenance attestation provenance

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

v7.0.4

1 finding
LOW No provenance attestation provenance

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

v7.0.3

1 finding
LOW No provenance attestation provenance

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

v7.0.2

1 finding
LOW No provenance attestation provenance

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

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

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