@meteora-ag/dlmm
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Known maintainer manual publish; no material diff vs prior approved version. | ai | |
| provenance | no-provenance | AI (provenance): Legacy manual publish flow; not a risk signal for this established package. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): express is a declared runtime dep used in an optional server entrypoint, not a true phantom. | ai | |
| phantom-deps | phantom-dep:@solana/buffer-layout | AI (phantom-deps): Solana ecosystem transitive usage; stable false positive for this package. | ai |
Versions (showing 51 of 85)
| Version | Deps | Published |
|---|---|---|
| 1.9.14 | 9 / 13 | |
| 1.9.13 | 9 / 13 | |
| 1.9.12 | 9 / 13 | |
| 1.9.11 | 9 / 13 | |
| 1.9.10 | 9 / 13 | |
| 1.9.9 | 9 / 13 | |
| 1.9.8 | 9 / 13 | |
| 1.9.7 | 9 / 13 | |
| 1.9.6 | 9 / 13 | |
| 1.9.4 | 9 / 13 | |
| 1.9.3 | 9 / 13 | |
| 1.9.2 | 9 / 13 | |
| 1.9.0 | 9 / 13 | |
| 1.8.0 | 9 / 13 | |
| 1.7.6 | 9 / 13 | |
| 1.7.5 | 9 / 13 | |
| 1.7.3 | 9 / 13 | |
| 1.7.2 | 9 / 13 | |
| 1.7.0 | 9 / 13 | |
| 1.6.1 | 9 / 13 | |
| 1.6.0 | 9 / 13 | |
| 1.5.5 | 9 / 13 | |
| 1.5.4 | 9 / 13 | |
| 1.5.3 | 9 / 13 | |
| 1.5.2 | 9 / 13 | |
| 1.5.1 | 9 / 13 | |
| 1.5.0 | 9 / 13 | |
| 1.4.11 | 9 / 13 | |
| 1.4.10 | 9 / 13 | |
| 1.4.9 | 9 / 13 | |
| 1.4.7 | 9 / 13 | |
| 1.4.6 | 9 / 13 | |
| 1.4.5 | 9 / 13 | |
| 1.4.4 | 9 / 13 | |
| 1.4.3 | 9 / 13 | |
| 1.4.2 | 9 / 13 | |
| 1.4.1 | 9 / 13 | |
| 1.4.0 | 9 / 13 | |
| 1.3.16 | 9 / 13 | |
| 1.3.15 | 9 / 13 | |
| 1.3.13 | 9 / 13 | |
| 1.3.12 | 9 / 13 | |
| 1.3.11 | 10 / 13 | |
| 1.3.10 | 10 / 13 | |
| 1.3.9 | 10 / 13 | |
| 1.3.8 | 10 / 13 | |
| 1.3.7 | 10 / 13 | |
| 1.3.6 | 10 / 13 | |
| 1.3.5 | 10 / 13 | |
| 1.3.4 | 10 / 13 | |
| 1.3.3 | 9 / 13 |
v1.9.14
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannweeeee.
v1.9.13
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannweeeee.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dannweeeee) than the most recent previously approved version (senddageeand4get) on 2026-07-10, but dannweeeee 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.9.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.11
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (senddageeand4get) than the most recent previously approved version (bangyro) on 2026-07-02, but senddageeand4get 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.9.10
2 findings[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 (senddageeand4get) than the most recent previously approved version (dannweeeee) on 2026-05-18, but senddageeand4get 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.9.9
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannweeeee.
This version was published by a different npm account (dannweeeee) than the most recent previously approved version (bangyro) on 2026-05-13, but dannweeeee 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.9.8
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannweeeee.
This version was published by a different npm account (dannweeeee) than the most recent previously approved version (bangyro) on 2026-05-13, but dannweeeee 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.9.3
3 findingsThis version was published by a different npm account (tokyobanana) than the most recent previously approved version (bangyro) on 2026-01-06. It has since remained available on npm for 192 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: tokyobanana.
v1.7.6
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dannweeeee.
This version was published by a different npm account (dannweeeee) than the most recent previously approved version (bangyro) on 2025-10-31, but dannweeeee 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.5
2 findingsThis version was published by a different npm account (bangyro) than the most recent previously approved version (mcsam94) on 2025-09-30. It has since remained available on npm for 290 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
2 findings[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 (mcsam94) than the most recent previously approved version (senddageeand4get) on 2025-09-03, but mcsam94 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[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 (mcsam94) than the most recent previously approved version (senddageeand4get) on 2025-08-28, but mcsam94 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.0
2 findingsThis version was published by a different npm account (senddageeand4get) than the most recent previously approved version (mcsam94) on 2025-08-21. It has since remained available on npm for 331 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
2 findings[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 (mcsam94) than the most recent previously approved version (codewithgun) on 2025-07-23, but mcsam94 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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
2 findings[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 (mcsam94) than the most recent previously approved version (codewithgun) on 2025-05-30, but mcsam94 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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dongnguyen91861) than the most recent previously approved version (mcsam94) on 2025-03-18, but dongnguyen91861 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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (dongnguyen91861) than the most recent previously approved version (mcsam94) on 2025-02-20, but dongnguyen91861 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.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.