@mdi/js
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @mdi/js is the canonical Material Design Icons JS package, not a typosquat of 'qs'. Scoped package name comparison by edit distance produces systematic false positives here. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): @mdi/js is a well-established icon library, not a typosquat of 'jest'. Levenshtein distance on scoped names is not meaningful here. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @mdi/js is a well-established icon library, not a typosquat of 'pg'. Levenshtein distance on scoped names is not meaningful here. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): @mdi/js is a well-established icon library, not a typosquat of 'rxjs'. Levenshtein distance on scoped names is not meaningful here. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @mdi/js is a well-established icon library, not a typosquat of 'joi'. Levenshtein distance on scoped names is not meaningful here. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @mdi/js is a well-established icon library, not a typosquat of 'ajv'. Levenshtein distance on scoped names is not meaningful here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 7.4.47 | 0 / 2 | |
| 7.3.67 | 0 / 2 | |
| 7.2.96 | 0 / 2 | |
| 7.1.96 | 0 / 2 | |
| 7.0.96 | 0 / 2 |
v7.3.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.