← Home

@linktr.ee/linkapp

npm

Development, build, and deployment tooling for LinkApps

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

Maintainers

chase-linktreezwparkerksavmarcus-linktreejeanikaakgupta89linktreegracemccartermrachamallulinktreewrenchessnickhenrylt-zachdaniel-linktreelt_mattogleericlinktreewayne-lincolnjoshquiaponleigh-karinjaweavaben.sauszach-lin-linktreecortl.eejesse.swickhams1luzheng_linktreenash-linktreejacobimpsonlinktreedarcylinktreemason.linktreeit-appsorlandojgubmanlucabernardinogenrmirandajacoblinktree2stlasallebradleyessaadurrfu-ltjerinraisaandrii.hanetsoleksandr-kucherukedbordin-linktreejameson-linktreevancegilliescarlesltroberterdinhuangjun604aimbermanjiayaoyuhakugzocoijoe-ltreedgpookaowensaldanhamruvysjazzbassjohnsonzacmartinotolseeashwini-ltmskonovalovlindsey-warrkunal94318jszklarz-ltalexb-linktreeigor-linktreeseanwangskmarshall-ltleilenahpatrickm-linktreeduongtran_linktreejake-ltcain88ltmichaelnathangathrightcolin-linktreejessieltjuantwoeesedfrey_linktrandrii.linktr.eedenys.h.linktreelouie-bertbriceyokoyamaoleksii.sievriukov.linktreeyuanlunaalxxjohnlinktree-luthermfs780icaro1508-ltmarcelo-ltadrianbrs-lttyler-linktreezander-linktreeregnullandrersfremedyedgesneamonitakisdorit-lt2carl-deguiagalacemiguelaj-abadomegdadimblodealexzaccatalinktreekhalid_treeglorison-ltlinkns

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-removed AI (maintainer-change): Same rationale — org-level team rotation, not a hostile takeover signal. ai
maintainer-change maintainer-added AI (maintainer-change): Linktree org package; maintainer rotation reflects normal team changes at a known company. ai
phantom-deps phantom-dep:warning AI (phantom-deps): Same pattern — config-referenced dep in a build tooling package. ai
phantom-deps phantom-dep:fs-extra AI (phantom-deps): Same pattern — config-referenced dep in a build tooling package. ai
phantom-deps phantom-dep:netrc-parser AI (phantom-deps): Same pattern — config-referenced dep in a build tooling package. ai
phantom-deps phantom-dep:class-variance-authority AI (phantom-deps): Same pattern — config-referenced dep in a build tooling package. ai
phantom-deps phantom-dep:@ngrok/ngrok AI (phantom-deps): Same pattern — config-referenced dep in a build tooling package. ai
phantom-deps phantom-dep:connect AI (phantom-deps): Build tooling package; deps referenced in config/runtime files, not direct imports. Stable FP. ai
phantom-deps phantom-dep:prop-types AI (phantom-deps): prop-types is a declared runtime dep used by bundled React components; phantom-dep heuristic is a false positive here. ai

Versions (showing 51 of 53)

View all versions
Version Deps Published
0.0.56 28 / 6
0.0.55 28 / 6
0.0.53 28 / 6
0.0.51 28 / 6
0.0.50 28 / 6
0.0.49 28 / 6
0.0.48 28 / 6
0.0.47 23 / 6
0.0.46 23 / 6
0.0.45 22 / 6
0.0.44 17 / 6
0.0.43 17 / 6
0.0.42 17 / 6
0.0.41 17 / 6
0.0.40 17 / 6
0.0.39 17 / 6
0.0.38 32 / 10
0.0.37 32 / 10
0.0.36 32 / 10
0.0.35 32 / 10
0.0.34 32 / 10
0.0.33 32 / 10
0.0.32 32 / 10
0.0.31 32 / 10
0.0.30 32 / 10
0.0.29 29 / 10
0.0.28 29 / 10
0.0.27 29 / 10
0.0.26 29 / 10
0.0.25 29 / 10
0.0.24 29 / 10
0.0.23 29 / 10
0.0.22 25 / 10
0.0.21 26 / 10
0.0.20 26 / 10
0.0.19 26 / 10
0.0.18 26 / 10
0.0.17 26 / 10
0.0.16 26 / 10
0.0.15 26 / 10
0.0.14 26 / 10
0.0.13 26 / 10
0.0.12 26 / 10
0.0.11 26 / 10
0.0.10 26 / 10
0.0.9 26 / 10
0.0.8 26 / 10
0.0.7 26 / 10
0.0.6 26 / 10
0.0.5 26 / 10
0.0.3 26 / 10

v0.0.56

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.

v0.0.55

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mblode.

LOW No provenance attestation provenance

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

v0.0.53

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: mblode.

LOW No provenance attestation provenance

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

v0.0.51

1 finding
LOW No provenance attestation provenance

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

v0.0.50

1 finding
LOW No provenance attestation provenance

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

v0.0.49

1 finding
LOW No provenance attestation provenance

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

v0.0.48

1 finding
LOW No provenance attestation provenance

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

v0.0.47

1 finding
LOW No provenance attestation provenance

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

v0.0.46

1 finding
LOW No provenance attestation provenance

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

v0.0.45

1 finding
LOW No provenance attestation provenance

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

v0.0.44

1 finding
LOW No provenance attestation provenance

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

v0.0.43

1 finding
LOW No provenance attestation provenance

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

v0.0.42

1 finding
LOW No provenance attestation provenance

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

v0.0.41

1 finding
LOW No provenance attestation provenance

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

v0.0.40

1 finding
LOW No provenance attestation provenance

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

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

v0.0.38

1 finding
LOW No provenance attestation provenance

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

v0.0.37

1 finding
LOW No provenance attestation provenance

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

v0.0.36

1 finding
LOW No provenance attestation provenance

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

v0.0.35

1 finding
LOW No provenance attestation provenance

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

v0.0.34

1 finding
LOW No provenance attestation provenance

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

v0.0.33

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.

v0.0.32

1 finding
LOW No provenance attestation provenance

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

v0.0.31

1 finding
LOW No provenance attestation provenance

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

v0.0.30

1 finding
LOW No provenance attestation provenance

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

v0.0.29

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.

v0.0.28

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.

v0.0.27

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.

v0.0.26

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.

v0.0.25

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.

v0.0.24

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.

v0.0.23

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.

v0.0.22

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.

v0.0.21

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.

v0.0.20

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.

v0.0.19

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.

v0.0.18

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.

v0.0.17

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.

v0.0.16

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.

v0.0.15

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.

v0.0.14

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.

v0.0.13

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.

v0.0.12

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.

v0.0.11

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.

v0.0.10

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.

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

v0.0.8

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.

v0.0.7

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.

v0.0.6

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.

v0.0.5

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.

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