@meshagent/meshagent
Meshagent Client
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yjs | AI (phantom-deps): yjs is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dependency; phantom-dep heuristic fires incorrectly for this package. | ai |
Versions (showing 100 of 174)
| Version | Deps | Published |
|---|---|---|
| 0.47.0 | 8 / 9 | |
| 0.46.4 | 8 / 9 | |
| 0.46.3 | 8 / 9 | |
| 0.46.2 | 8 / 9 | |
| 0.46.1 | 8 / 9 | |
| 0.46.0 | 8 / 9 | |
| 0.45.7 | 8 / 9 | |
| 0.45.6 | 8 / 9 | |
| 0.45.5 | 8 / 9 | |
| 0.45.4 | 8 / 9 | |
| 0.45.2 | 8 / 9 | |
| 0.45.1 | 8 / 9 | |
| 0.45.0 | 8 / 9 | |
| 0.44.13 | 8 / 9 | |
| 0.44.12 | 8 / 9 | |
| 0.44.11 | 8 / 9 | |
| 0.44.10 | 8 / 9 | |
| 0.44.9 | 8 / 9 | |
| 0.44.8 | 8 / 9 | |
| 0.44.7 | 8 / 9 | |
| 0.44.6 | 8 / 9 | |
| 0.44.5 | 8 / 9 | |
| 0.44.4 | 8 / 9 | |
| 0.44.3 | 8 / 9 | |
| 0.44.1 | 8 / 9 | |
| 0.44.0 | 8 / 9 | |
| 0.43.3 | 8 / 9 | |
| 0.43.2 | 8 / 9 | |
| 0.43.1 | 8 / 9 | |
| 0.43.0 | 8 / 9 | |
| 0.42.2 | 9 / 9 | |
| 0.42.0 | 9 / 9 | |
| 0.41.9 | 9 / 9 | |
| 0.41.7 | 9 / 9 | |
| 0.41.6 | 9 / 9 | |
| 0.41.5 | 9 / 9 | |
| 0.41.4 | 9 / 9 | |
| 0.41.2 | 9 / 9 | |
| 0.41.1 | 9 / 9 | |
| 0.41.0 | 9 / 9 | |
| 0.40.2 | 9 / 9 | |
| 0.40.1 | 9 / 9 | |
| 0.40.0 | 9 / 9 | |
| 0.39.9 | 9 / 9 | |
| 0.39.8 | 9 / 9 | |
| 0.39.7 | 9 / 9 | |
| 0.39.6 | 9 / 9 | |
| 0.39.5 | 9 / 9 | |
| 0.39.4 | 9 / 9 | |
| 0.39.3 | 9 / 9 | |
| 0.39.2 | 9 / 9 | |
| 0.39.1 | 9 / 9 | |
| 0.39.0 | 9 / 9 | |
| 0.38.4 | 8 / 9 | |
| 0.38.3 | 8 / 9 | |
| 0.38.2 | 8 / 9 | |
| 0.38.1 | 8 / 9 | |
| 0.38.0 | 8 / 9 | |
| 0.37.2 | 8 / 9 | |
| 0.37.1 | 8 / 9 | |
| 0.37.0 | 8 / 9 | |
| 0.36.3 | 8 / 9 | |
| 0.36.2 | 8 / 9 | |
| 0.36.1 | 8 / 9 | |
| 0.36.0 | 8 / 9 | |
| 0.35.8 | 8 / 9 | |
| 0.35.7 | 8 / 9 | |
| 0.35.6 | 8 / 9 | |
| 0.35.5 | 8 / 9 | |
| 0.35.4 | 8 / 9 | |
| 0.35.3 | 8 / 9 | |
| 0.35.0 | 8 / 9 | |
| 0.34.0 | 8 / 9 | |
| 0.33.3 | 8 / 9 | |
| 0.33.2 | 8 / 9 | |
| 0.33.1 | 8 / 9 | |
| 0.33.0 | 8 / 9 | |
| 0.32.0 | 8 / 9 | |
| 0.31.4 | 8 / 9 | |
| 0.31.3 | 8 / 9 | |
| 0.31.2 | 8 / 9 | |
| 0.31.1 | 8 / 9 | |
| 0.31.0 | 8 / 9 | |
| 0.30.1 | 8 / 9 | |
| 0.30.0 | 8 / 9 | |
| 0.29.4 | 8 / 9 | |
| 0.29.2 | 8 / 9 | |
| 0.29.1 | 8 / 9 | |
| 0.29.0 | 8 / 9 | |
| 0.28.15 | 8 / 9 | |
| 0.28.14 | 8 / 9 | |
| 0.28.13 | 8 / 9 | |
| 0.28.12 | 8 / 9 | |
| 0.28.11 | 8 / 9 | |
| 0.28.10 | 8 / 9 | |
| 0.28.9 | 8 / 9 | |
| 0.28.8 | 8 / 9 | |
| 0.28.7 | 8 / 9 | |
| 0.28.6 | 8 / 9 | |
| 0.28.5 | 8 / 9 |
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.