@desource/phone-mask-nuxt
🎯 Zero-config Nuxt module for international phone masking. Powered by @desource/phone-mask with Google libphonenumber sync.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| dependencies | unvetted-dep:@desource/phone-mask-vue | AI (dependencies): Same-org monorepo sibling package; expected dependency for this Nuxt wrapper. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 1 / 6 | |
| 1.3.0 | 1 / 6 | |
| 1.2.0 | 1 / 6 | |
| 1.1.2 | 1 / 6 | |
| 1.1.1 | 1 / 5 | |
| 1.1.0 | 1 / 5 | |
| 1.0.0 | 1 / 5 | |
| 0.3.0 | 1 / 4 | |
| 0.2.3 | 1 / 4 | |
| 0.2.2 | 1 / 4 |
v1.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.