@appland/components
This repository bundles together AppMap models and Vue components in a single dependency.
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:lucide-vue | AI (phantom-deps): Component library; dependencies loaded via config/convention, not direct imports. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:mermaid | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:dompurify | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:js-base64 | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/sax | AI (phantom-deps): Framework-scoped package loaded by convention; stable for this package. | ai | |
| phantom-deps | phantom-dep:dom-to-svg | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:highlight.js | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:sql-formatter | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:d3-flame-graph | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:marked-highlight | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:sax | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:diff | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:pako | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:events | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:marked | AI (phantom-deps): Referenced in config files; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:vuex | AI (phantom-deps): Vuex is a peer/bundled dep; phantom-dep heuristic is a stable false positive for this Vue component library. | ai | |
| phantom-deps | phantom-dep:d3 | AI (phantom-deps): d3 is bundled into dist; phantom-dep heuristic is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@appland/rpc | AI (phantom-deps): Same-org dep; phantom-dep heuristic is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@appland/client | AI (phantom-deps): Same-org dep; phantom-dep heuristic is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@appland/models | AI (phantom-deps): Same-org dep; phantom-dep heuristic is a stable false positive. | ai | |
| phantom-deps | phantom-dep:@appland/diagrams | AI (phantom-deps): Same-org dep; phantom-dep heuristic is a stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README link dump signal is a false positive for a component library that links to its monorepo docs. | ai | |
| phantom-deps | phantom-dep:vue | AI (phantom-deps): Vue is a peer/bundled dep in a Vue component library; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@appland/sequence-diagram | AI (phantom-deps): Same-org dep; phantom-dep heuristic is a stable false positive. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 4.49.0 | 25 / 69 | |
| 4.48.0 | 25 / 72 | |
| 4.47.0 | 25 / 72 | |
| 4.46.4 | 24 / 72 | |
| 4.46.3 | 24 / 72 | |
| 4.46.2 | 24 / 72 | |
| 4.46.1 | 24 / 72 | |
| 4.46.0 | 24 / 72 | |
| 4.45.0 | 24 / 72 | |
| 4.44.0 | 24 / 72 | |
| 4.43.2 | 24 / 72 | |
| 4.43.1 | 24 / 72 | |
| 4.43.0 | 24 / 72 | |
| 4.42.0 | 24 / 72 | |
| 4.41.0 | 24 / 72 | |
| 4.40.1 | 24 / 72 | |
| 4.40.0 | 24 / 72 | |
| 4.39.3 | 24 / 72 | |
| 4.39.2 | 24 / 72 | |
| 4.39.1 | 24 / 72 | |
| 4.39.0 | 24 / 72 | |
| 4.38.3 | 24 / 72 | |
| 4.38.2 | 24 / 72 | |
| 4.38.1 | 24 / 72 | |
| 4.38.0 | 24 / 72 | |
| 4.37.4 | 24 / 72 | |
| 4.37.3 | 24 / 72 | |
| 4.37.2 | 24 / 72 | |
| 4.37.1 | 24 / 72 | |
| 4.37.0 | 24 / 72 | |
| 4.36.0 | 24 / 72 | |
| 4.35.0 | 24 / 72 | |
| 4.34.0 | 22 / 72 | |
| 4.33.1 | 22 / 72 | |
| 4.33.0 | 22 / 72 | |
| 4.32.1 | 22 / 72 | |
| 4.32.0 | 22 / 72 | |
| 4.31.1 | 22 / 72 | |
| 4.31.0 | 22 / 72 | |
| 4.30.1 | 22 / 72 | |
| 4.30.0 | 22 / 72 | |
| 4.29.0 | 22 / 72 | |
| 4.28.1 | 22 / 72 | |
| 4.28.0 | 22 / 72 | |
| 4.27.1 | 22 / 72 | |
| 4.27.0 | 22 / 72 | |
| 4.26.0 | 19 / 71 | |
| 4.25.0 | 19 / 71 | |
| 4.24.4 | 19 / 71 | |
| 4.24.3 | 19 / 71 | |
| 4.24.2 | 19 / 71 | |
| 4.24.1 | 19 / 71 | |
| 4.24.0 | 19 / 71 | |
| 4.23.0 | 19 / 71 | |
| 4.22.1 | 19 / 71 | |
| 4.22.0 | 19 / 71 | |
| 4.21.0 | 19 / 71 | |
| 4.20.0 | 19 / 71 | |
| 4.19.1 | 19 / 71 | |
| 4.19.0 | 19 / 71 | |
| 4.18.0 | 19 / 71 | |
| 4.17.0 | 19 / 71 | |
| 4.16.2 | 19 / 71 | |
| 4.16.1 | 19 / 71 | |
| 4.16.0 | 19 / 71 | |
| 4.14.0 | 19 / 71 | |
| 4.13.0 | 19 / 71 | |
| 4.12.2 | 19 / 71 | |
| 4.12.1 | 19 / 71 | |
| 4.12.0 | 19 / 71 | |
| 4.11.0 | 19 / 71 | |
| 4.10.0 | 19 / 71 | |
| 4.9.0 | 19 / 71 | |
| 4.8.2 | 19 / 71 | |
| 4.8.1 | 19 / 71 | |
| 4.8.0 | 19 / 71 | |
| 4.7.0 | 19 / 71 | |
| 4.6.0 | 19 / 71 | |
| 4.5.0 | 19 / 71 | |
| 4.4.0 | 19 / 71 | |
| 4.3.0 | 19 / 71 | |
| 4.2.1 | 19 / 71 | |
| 4.2.0 | 19 / 71 | |
| 4.1.0 | 19 / 71 | |
| 4.0.0 | 19 / 71 |
v4.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.42.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.