@axinom/mosaic-ui
UI components for building Axinom Mosaic 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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Axinom org package with 950 prior versions and vetted publisher; gap likely reflects internal release cadence change. | ai | |
| dependencies | unvetted-dep:@mui/base | AI (dependencies): @mui/base is a well-known MUI package; beta pin is intentional for this UI library. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): postcss is a build-time dep used via rollup-plugin-postcss; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@axinom/mosaic-core | AI (phantom-deps): Same-org dependency; phantom-dep heuristic unreliable for monorepo/workspace packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Proprietary internal UI library; no public repo or README code blocks expected for this package type. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.71.0 | 18 / 51 | |
| 0.70.0 | 18 / 51 | |
| 0.69.0 | 18 / 51 | |
| 0.68.3 | 18 / 50 | |
| 0.68.2 | 18 / 50 | |
| 0.68.1 | 18 / 50 | |
| 0.68.0 | 18 / 50 | |
| 0.67.0 | 18 / 50 | |
| 0.66.2 | 18 / 50 | |
| 0.66.1 | 18 / 50 | |
| 0.66.0 | 18 / 50 |
v0.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.68.0
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 (axinomnpm) than the most recent previously approved version (ruwanx) on 2026-02-26, but axinomnpm 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.
v0.67.0
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 (axinomnpm) than the most recent previously approved version (ruwanx) on 2026-01-14, but axinomnpm 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.
v0.66.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 (ruwanx) than the most recent previously approved version (axinomnpm) on 2025-11-25, but ruwanx 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.
v0.66.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.