@meshmakers/octo-ui
Angular library providing reusable UI components for OctoMesh 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:fesm2022/meshmakers-octo-ui-branding-settings.mjs | AI (source-diff): Standard Angular fesm2022 bundle output; long lines are inlined templates, not obfuscation. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known Angular/TypeScript implicit runtime dep; stable false positive for this package. | ai |
Versions (showing 51 of 138)
| Version | Deps | Published |
|---|---|---|
| 3.3.1200 | 1 / 0 | |
| 3.3.1190 | 1 / 0 | |
| 3.3.1180 | 1 / 0 | |
| 3.3.1170 | 1 / 0 | |
| 3.3.1160 | 1 / 0 | |
| 3.3.1150 | 1 / 0 | |
| 3.3.1140 | 1 / 0 | |
| 3.3.1130 | 1 / 0 | |
| 3.3.1120 | 1 / 0 | |
| 3.3.1110 | 1 / 0 | |
| 3.3.1100 | 1 / 0 | |
| 3.3.1090 | 1 / 0 | |
| 3.3.1080 | 1 / 0 | |
| 3.3.1070 | 1 / 0 | |
| 3.3.1060 | 1 / 0 | |
| 3.3.1050 | 1 / 0 | |
| 3.3.1040 | 1 / 0 | |
| 3.3.1030 | 1 / 0 | |
| 3.3.1020 | 1 / 0 | |
| 3.3.1010 | 1 / 0 | |
| 3.3.1000 | 1 / 0 | |
| 3.3.980 | 1 / 0 | |
| 3.3.970 | 1 / 0 | |
| 3.3.960 | 1 / 0 | |
| 3.3.950 | 1 / 0 | |
| 3.3.940 | 1 / 0 | |
| 3.3.930 | 1 / 0 | |
| 3.3.920 | 1 / 0 | |
| 3.3.910 | 1 / 0 | |
| 3.3.900 | 1 / 0 | |
| 3.3.890 | 1 / 0 | |
| 3.3.880 | 1 / 0 | |
| 3.3.870 | 1 / 0 | |
| 3.3.860 | 1 / 0 | |
| 3.3.850 | 1 / 0 | |
| 3.3.840 | 1 / 0 | |
| 3.3.830 | 1 / 0 | |
| 3.3.820 | 1 / 0 | |
| 3.3.810 | 1 / 0 | |
| 3.3.800 | 1 / 0 | |
| 3.3.790 | 1 / 0 | |
| 3.3.780 | 1 / 0 | |
| 3.3.770 | 1 / 0 | |
| 3.3.760 | 1 / 0 | |
| 3.3.750 | 1 / 0 | |
| 3.3.740 | 1 / 0 | |
| 3.3.730 | 1 / 0 | |
| 3.3.720 | 1 / 0 | |
| 3.3.710 | 1 / 0 | |
| 3.3.700 | 1 / 0 | |
| 3.3.690 | 1 / 0 |
v3.3.1200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1190
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1180
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1170
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1160
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1110
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1090
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1080
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1070
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1060
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1050
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1040
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1030
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1020
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1010
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1000
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.980
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.970
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.960
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.950
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.940
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.930
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.920
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.910
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.890
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.880
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.870
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.860
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.850
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.840
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.830
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.810
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.800
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.790
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.780
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.770
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.760
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.750
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.740
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.730
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.720
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.710
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.700
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.690
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.