@linktr.ee/messaging-react
React messaging components built on messaging-core for web applications
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/Card-Bp3XzYXV.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React UI logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/LockedThumbnail-DR1i_N1L.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React UI component logic. | ai | |
| source-diff | obfuscated-file:dist/index-Dgh0_9UW.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React/messaging provider logic. | ai | |
| source-diff | obfuscated-file:dist/index-B5KGQRPs.cjs | AI (source-diff): Standard Vite minified bundle output; readable React/messaging logic in sample, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/Card-CCXUxcTf.cjs | AI (source-diff): Standard Vite minified bundle output; readable React component logic in sample, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/LockedThumbnail-BWaey0lS.cjs | AI (source-diff): Standard Vite minified bundle output; readable React component logic in sample, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/Card-Cq0x0bbb.cjs | AI (source-diff): Standard Vite minified CJS bundle; readable React component logic visible in sample. | ai | |
| source-diff | obfuscated-file:dist/LockedThumbnail--h4GTH41.cjs | AI (source-diff): Standard Vite minified CJS bundle; readable React component logic visible in sample. | ai | |
| source-diff | obfuscated-file:dist/index-DqNobxVj.cjs | AI (source-diff): Standard Vite minified CJS bundle; readable provider/context logic with debug logs visible in sample. | ai | |
| source-diff | obfuscated-file:dist/Card-D2KIDqPs.cjs | AI (source-diff): Standard Vite minified CJS bundle; readable React component code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/index-DuGzAVyy.cjs | AI (source-diff): Standard Vite minified CJS bundle; readable React/messaging provider code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/LockedThumbnail-CD9YTQ0r.cjs | AI (source-diff): Standard Vite minified CJS bundle; readable React component code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/index-CQ913euH.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React/stream-chat integration logic. | ai | |
| source-diff | obfuscated-file:dist/Card-CexShqpK.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React logic, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/LockedThumbnail-CydtYOSA.cjs | AI (source-diff): Standard Vite minified bundle output; code is readable React component logic. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump for an internal Linktree package; large file additions are expected from a significant refactor. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-internal package; adding team members is routine for @linktr.ee scope. | ai | |
| dependencies | unvetted-dep:@linktr.ee/component-library | AI (dependencies): Same org scope (@linktr.ee); internal dependency, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@linktr.ee/messaging-core | AI (dependencies): Same org scope (@linktr.ee); internal dependency, stable pattern across versions. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Intentionally proprietary/private package; UNLICENSED is expected for this org's internal libraries. | ai | |
| provenance | no-provenance | AI (provenance): Internal Linktree org package; provenance absence is consistent across all 213 versions and poses no elevated risk here. | ai | |
| phantom-deps | phantom-dep:@linktr.ee/component-library | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via CSS/types rather than direct import. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 3 / 30 | |
| 2.5.2 | 3 / 30 | |
| 2.4.4 | 3 / 30 | |
| 2.3.3 | 3 / 30 | |
| 2.3.0 | 3 / 30 | |
| 2.2.0 | 3 / 30 | |
| 2.0.0 | 3 / 30 | |
| 1.40.2 | 3 / 30 | |
| 1.40.1 | 3 / 30 | |
| 1.40.0 | 3 / 30 | |
| 1.39.0 | 3 / 30 | |
| 1.38.0 | 3 / 30 | |
| 1.34.0 | 3 / 30 | |
| 1.33.3 | 3 / 30 | |
| 1.33.2 | 3 / 30 | |
| 1.32.1 | 3 / 30 | |
| 1.31.0 | 3 / 30 | |
| 1.29.1 | 3 / 30 | |
| 1.29.0 | 4 / 29 | |
| 1.28.1 | 4 / 29 | |
| 1.26.1 | 4 / 29 | |
| 1.25.1 | 4 / 29 | |
| 1.24.4 | 4 / 29 | |
| 1.24.3 | 4 / 29 | |
| 1.24.1 | 4 / 29 | |
| 1.22.1 | 4 / 29 | |
| 1.22.0 | 4 / 29 | |
| 1.21.2 | 4 / 29 | |
| 1.21.1 | 4 / 29 | |
| 1.21.0 | 4 / 29 | |
| 1.20.0 | 4 / 29 | |
| 1.17.0 | 4 / 29 | |
| 1.15.2 | 4 / 29 | |
| 1.12.3 | 4 / 29 | |
| 1.9.2 | 4 / 29 | |
| 1.9.0 | 4 / 29 | |
| 1.7.0 | 4 / 29 | |
| 1.6.4 | 4 / 29 |
v3.0.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lt_mattogle) than the most recent previously approved version (darcylinktree) on 2026-05-28, but lt_mattogle 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.
v2.3.3
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lt_mattogle) than the most recent previously approved version (darcylinktree) on 2026-05-26, but lt_mattogle 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.
v2.3.0
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lt_mattogle) than the most recent previously approved version (darcylinktree) on 2026-05-22, but lt_mattogle 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.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.