← Home

@heliofi/launchpad-common

npm
100
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.

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Known maintainer resuming publishing; no malicious payload in diff. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer matches existing known name per provenance info. ai
publish-pattern new-deps-added AI (publish-pattern): buffer is a standard well-known polyfill, not a supply-chain risk. ai
phantom-deps phantom-dep:bs58 AI (phantom-deps): Config-only reference, consistent with monorepo shared package pattern. ai

Versions (showing 100 of 118)

Version Deps Published
1.7.40 8 / 6
1.7.39 8 / 6
1.7.37 8 / 6
1.7.36 8 / 6
1.7.35 8 / 6
1.7.34 8 / 6
1.7.33 8 / 6
1.7.32 8 / 6
1.7.31 8 / 6
1.7.30 8 / 6
1.7.29 8 / 6
1.7.28 8 / 6
1.7.27 8 / 6
1.7.26 8 / 6
1.7.25 7 / 5
1.7.24 7 / 5
1.7.23 7 / 5
1.7.22 7 / 5
1.7.21 7 / 5
1.7.20 7 / 5
1.7.19 7 / 5
1.7.18 7 / 5
1.7.17 7 / 5
1.7.16 7 / 5
1.7.15 7 / 5
1.7.14 7 / 5
1.7.12 7 / 5
1.7.11 7 / 5
1.7.10 7 / 5
1.7.9 7 / 5
1.7.8 7 / 5
1.7.7 7 / 5
1.7.6 7 / 5
1.7.5 7 / 5
1.7.4 7 / 5
1.7.3 7 / 5
1.7.2 7 / 5
1.7.1 7 / 5
1.6.54 7 / 5
1.6.53 7 / 5
1.6.52 7 / 5
1.6.51 7 / 5
1.6.50 7 / 5
1.6.49 7 / 5
1.6.48 7 / 5
1.6.47 7 / 5
1.6.46 7 / 5
1.6.45 7 / 5
1.6.44 7 / 5
1.6.43 7 / 5
1.6.42 7 / 5
1.6.41 7 / 5
1.6.39 7 / 5
1.6.38 7 / 5
1.6.37 7 / 5
1.6.36 7 / 5
1.6.35 7 / 5
1.6.34 7 / 5
1.6.33 7 / 5
1.6.32 7 / 5
1.6.31 7 / 5
1.6.30 7 / 5
1.6.29 7 / 5
1.6.28 7 / 5
1.6.27 7 / 5
1.6.26 7 / 5
1.6.25 7 / 5
1.6.24 7 / 4
1.6.23 7 / 4
1.6.22 7 / 4
1.6.21 6 / 4
1.6.20 6 / 4
1.6.19 6 / 4
1.6.18 6 / 4
1.6.17 6 / 4
1.6.16 6 / 4
1.6.15 6 / 4
1.6.14 7 / 4
1.6.11 7 / 4
1.6.10 7 / 4
1.6.9 7 / 4
1.6.8 7 / 4
1.6.6 7 / 4
1.6.5 7 / 4
1.6.4 7 / 4
1.6.3 7 / 4
1.6.1 7 / 4
1.5.9 7 / 4
1.5.8 6 / 4
1.5.7 6 / 4
1.5.6 6 / 4
1.5.5 6 / 4
1.5.3 6 / 4
1.5.1 6 / 4
1.5.0 6 / 4
1.4.0 6 / 4
1.3.8 6 / 4
1.3.7 6 / 4
1.3.6 6 / 4
1.3.5 6 / 4
Showing 100 of 118 Next page →

v1.7.40

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.

v1.7.39

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.

v1.7.37

1 finding
LOW No provenance attestation provenance

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

v1.7.36

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: hhenryhharris → xyz1hang (on 2025-11-17, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (hhenryhharris) on 2025-11-17, but xyz1hang 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.

v1.7.35

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: hhenryhharris → bartoszlhelio (on 2025-11-07, known maintainer) provenance

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

v1.7.34

1 finding
LOW No provenance attestation provenance

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

v1.7.33

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: hhenryhharris → xyz1hang (on 2025-10-15, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (hhenryhharris) on 2025-10-15, but xyz1hang 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.

v1.7.32

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: hhenryhharris → xyz1hang (on 2025-10-13, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (hhenryhharris) on 2025-10-13, but xyz1hang 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.

v1.7.31

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: hhenryhharris → xyz1hang (on 2025-10-13, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (hhenryhharris) on 2025-10-13, but xyz1hang 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.

v1.7.30

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: hhenryhharris → bartoszlhelio (on 2025-10-03, known maintainer) provenance

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

v1.7.29

1 finding
LOW No provenance attestation provenance

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

v1.7.28

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: hhenryhharris → xyz1hang (on 2025-09-25, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (hhenryhharris) on 2025-09-25, but xyz1hang 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.

v1.7.27

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: hhenryhharris → bartoszlhelio (on 2025-09-08, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (hhenryhharris) on 2025-09-08, but bartoszlhelio 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.

v1.7.26

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: hhenryhharris → bartoszlhelio (on 2025-08-28, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (hhenryhharris) on 2025-08-28, but bartoszlhelio 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.

v1.7.25

1 finding
LOW No provenance attestation provenance

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

v1.7.24

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: hhenryhharris → xyz1hang (on 2025-08-05, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (hhenryhharris) on 2025-08-05, but xyz1hang 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.

v1.7.23

1 finding
LOW No provenance attestation provenance

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

v1.7.22

1 finding
LOW No provenance attestation provenance

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

v1.7.21

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: martinavagyan → hhenryhharris (on 2025-08-05, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (martinavagyan) on 2025-08-05, but hhenryhharris 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.

v1.7.20

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: martinavagyan → hhenryhharris (on 2025-08-01, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (martinavagyan) on 2025-08-01, but hhenryhharris 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.

v1.7.19

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: hhenryhharris → martinavagyan (on 2025-07-30, known maintainer) provenance

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

v1.7.18

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: hhenryhharris → martinavagyan (on 2025-07-30, known maintainer) provenance

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

v1.7.17

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: xyz1hang → hhenryhharris (on 2025-07-29, known maintainer) provenance

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

v1.7.16

1 finding
LOW No provenance attestation provenance

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

v1.7.15

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: tigran-helio → xyz1hang (on 2025-07-25, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (tigran-helio) on 2025-07-25, but xyz1hang 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.

v1.7.14

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: tigran-helio → hhenryhharris (on 2025-07-21, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (tigran-helio) on 2025-07-21, but hhenryhharris 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.

v1.7.12

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: hhenryhharris → tigran-helio (on 2025-07-17, known maintainer) provenance

This version was published by a different npm account (tigran-helio) than the most recent previously approved version (hhenryhharris) on 2025-07-17, but tigran-helio 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.

v1.7.11

1 finding
LOW No provenance attestation provenance

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

v1.7.10

1 finding
LOW No provenance attestation provenance

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

v1.7.9

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.

v1.7.8

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: hhenryhharris → tigran-helio (on 2025-07-09, known maintainer) provenance

This version was published by a different npm account (tigran-helio) than the most recent previously approved version (hhenryhharris) on 2025-07-09, but tigran-helio 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.

v1.7.7

1 finding
LOW No provenance attestation provenance

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

v1.7.6

1 finding
LOW No provenance attestation provenance

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

v1.7.5

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

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

v1.7.4

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: xyz1hang → bartoszlhelio (on 2025-06-26, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (xyz1hang) on 2025-06-26, but bartoszlhelio 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.

v1.7.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: bartoszlhelio → xyz1hang (on 2025-06-18, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (bartoszlhelio) on 2025-06-18, but xyz1hang 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.

v1.7.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: bartoszlhelio → hhenryhharris (on 2025-06-18, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (bartoszlhelio) on 2025-06-18, but hhenryhharris 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.

v1.7.1

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: xyz1hang → bartoszlhelio (on 2025-06-17, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (xyz1hang) on 2025-06-17, but bartoszlhelio 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.

v1.6.54

1 finding
LOW No provenance attestation provenance

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

v1.6.53

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: bartoszlhelio → xyz1hang (on 2025-06-12, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (bartoszlhelio) on 2025-06-12, but xyz1hang 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.

v1.6.52

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: bartoszlhelio → xyz1hang (on 2025-06-12, known maintainer) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (bartoszlhelio) on 2025-06-12, but xyz1hang 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.

v1.6.51

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: xyz1hang → bartoszlhelio (on 2025-06-12, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (xyz1hang) on 2025-06-12, but bartoszlhelio 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.

v1.6.50

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: xyz1hang → hhenryhharris (on 2025-06-12, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (xyz1hang) on 2025-06-12, but hhenryhharris 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.

v1.6.49

1 finding
LOW No provenance attestation provenance

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

v1.6.48

1 finding
LOW No provenance attestation provenance

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

v1.6.47

2 findings
MEDIUM Publisher changed: bartoszlhelio → xyz1hang (on 2025-06-03, unremoved on npm for 411d) provenance

This version was published by a different npm account (xyz1hang) than the most recent previously approved version (bartoszlhelio) on 2025-06-03. It has since remained available on npm for 411 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.

v1.6.46

1 finding
LOW No provenance attestation provenance

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

v1.6.45

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: 00mb → bartoszlhelio (on 2025-05-30, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (00mb) on 2025-05-30, but bartoszlhelio 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.

v1.6.44

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: 00mb → bartoszlhelio (on 2025-05-19, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (00mb) on 2025-05-19, but bartoszlhelio 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.

v1.6.43

1 finding
LOW No provenance attestation provenance

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

v1.6.42

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: 00mb → hhenryhharris (on 2025-05-14, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (00mb) on 2025-05-14, but hhenryhharris 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.

v1.6.41

1 finding
LOW No provenance attestation provenance

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

v1.6.39

1 finding
LOW No provenance attestation provenance

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

v1.6.38

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: bartoszlhelio → 00mb (on 2025-05-02, known maintainer) provenance

This version was published by a different npm account (00mb) than the most recent previously approved version (bartoszlhelio) on 2025-05-02, but 00mb 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.

v1.6.37

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: a2048 → bartoszlhelio (on 2025-04-30, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (a2048) on 2025-04-30, but bartoszlhelio 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.

v1.6.36

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: hhenryhharris → a2048 (on 2025-04-25, known maintainer) provenance

This version was published by a different npm account (a2048) than the most recent previously approved version (hhenryhharris) on 2025-04-25, but a2048 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.

v1.6.35

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: martinavagyan → hhenryhharris (on 2025-04-23, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (martinavagyan) on 2025-04-23, but hhenryhharris 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.

v1.6.34

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: hhenryhharris → martinavagyan (on 2025-04-17, known maintainer) provenance

This version was published by a different npm account (martinavagyan) than the most recent previously approved version (hhenryhharris) on 2025-04-17, but martinavagyan 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.

v1.6.33

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: bartoszlhelio → hhenryhharris (on 2025-04-17, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (bartoszlhelio) on 2025-04-17, but hhenryhharris 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.

v1.6.32

1 finding
LOW No provenance attestation provenance

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

v1.6.31

1 finding
LOW No provenance attestation provenance

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

v1.6.30

1 finding
LOW No provenance attestation provenance

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

v1.6.29

1 finding
LOW No provenance attestation provenance

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

v1.6.28

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: hhenryhharris → bartoszlhelio (on 2025-04-08, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (hhenryhharris) on 2025-04-08, but bartoszlhelio 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.

v1.6.27

1 finding
LOW No provenance attestation provenance

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

v1.6.26

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: bartoszlhelio → hhenryhharris (on 2025-04-01, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (bartoszlhelio) on 2025-04-01, but hhenryhharris 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.

v1.6.25

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: hhenryhharris → bartoszlhelio (on 2025-03-27, known maintainer) provenance

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

v1.6.24

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: bartoszlhelio → hhenryhharris (on 2025-03-27, known maintainer) provenance

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

v1.6.23

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: a2048 → bartoszlhelio (on 2025-03-27, known maintainer) provenance

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

v1.6.22

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: bartoszlhelio → a2048 (on 2025-03-26, known maintainer) provenance

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

v1.6.21

1 finding
LOW No provenance attestation provenance

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

v1.6.20

1 finding
LOW No provenance attestation provenance

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

v1.6.19

1 finding
LOW No provenance attestation provenance

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

v1.6.18

1 finding
LOW No provenance attestation provenance

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

v1.6.17

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: martinavagyan → bartoszlhelio (on 2025-03-14, known maintainer) provenance

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

v1.6.16

1 finding
LOW No provenance attestation provenance

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

v1.6.15

1 finding
LOW No provenance attestation provenance

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

v1.6.14

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: hhenryhharris → martinavagyan (on 2025-03-03, known maintainer) provenance

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

v1.6.11

1 finding
LOW No provenance attestation provenance

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

v1.6.10

1 finding
LOW No provenance attestation provenance

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

v1.6.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: bartoszlhelio → hhenryhharris (on 2025-02-27, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (bartoszlhelio) on 2025-02-27, but hhenryhharris 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.

v1.6.8

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: hhenryhharris → bartoszlhelio (on 2025-02-26, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (hhenryhharris) on 2025-02-26, but bartoszlhelio 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.

v1.6.6

1 finding
LOW No provenance attestation provenance

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

v1.6.5

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: martinavagyan → hhenryhharris (on 2025-02-25, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (martinavagyan) on 2025-02-25, but hhenryhharris 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.

v1.6.4

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: bartoszlhelio → martinavagyan (on 2025-02-20, known maintainer) provenance

This version was published by a different npm account (martinavagyan) than the most recent previously approved version (bartoszlhelio) on 2025-02-20, but martinavagyan 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.

v1.6.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: martinavagyan → bartoszlhelio (on 2025-02-20, known maintainer) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (martinavagyan) on 2025-02-20, but bartoszlhelio 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.

v1.6.1

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: hhenryhharris → martinavagyan (on 2025-02-18, known maintainer) provenance

This version was published by a different npm account (martinavagyan) than the most recent previously approved version (hhenryhharris) on 2025-02-18, but martinavagyan 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.

v1.5.9

1 finding
LOW No provenance attestation provenance

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

v1.5.8

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: ib1 → hhenryhharris (on 2025-02-07, known maintainer) provenance

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

v1.5.7

1 finding
LOW No provenance attestation provenance

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

v1.5.6

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: bartoszlhelio → ib1 (on 2025-02-06, known maintainer) provenance

This version was published by a different npm account (ib1) than the most recent previously approved version (bartoszlhelio) on 2025-02-06, but ib1 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.

v1.5.5

2 findings
MEDIUM Publisher changed: ib1 → bartoszlhelio (on 2025-01-22, unremoved on npm for 542d) provenance

This version was published by a different npm account (bartoszlhelio) than the most recent previously approved version (ib1) on 2025-01-22. It has since remained available on npm for 542 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.

v1.5.3

1 finding
LOW No provenance attestation provenance

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

v1.5.1

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: 00mb → ib1 (on 2025-01-22, known maintainer) provenance

This version was published by a different npm account (ib1) than the most recent previously approved version (00mb) on 2025-01-22, but ib1 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.

v1.5.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: hhenryhharris → 00mb (on 2025-01-16, known maintainer) provenance

This version was published by a different npm account (00mb) than the most recent previously approved version (hhenryhharris) on 2025-01-16, but 00mb 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.

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.8

1 finding
LOW No provenance attestation provenance

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

v1.3.7

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: ib1 → hhenryhharris (on 2025-01-06, known maintainer) provenance

This version was published by a different npm account (hhenryhharris) than the most recent previously approved version (ib1) on 2025-01-06, but hhenryhharris 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.

v1.3.6

1 finding
LOW No provenance attestation provenance

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

v1.3.5

1 finding
LOW No provenance attestation provenance

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