@jskit-ai/users-web
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
mercmobily
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher with strong track record; no material code changes; likely CI environment change rather than malicious intent. | ai | |
| provenance | no-provenance | AI (provenance): Common for org-scoped internal packages; stable across versions. | ai | |
| phantom-deps | phantom-dep:@mdi/js | AI (phantom-deps): @mdi/js is a declared runtime dep used indirectly via Vue components; phantom-dep heuristic is a stable false positive here. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal monorepo-style package; missing description is consistent across the @jskit-ai namespace. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @jskit-ai scoped package; sparse metadata is consistent across the org, not a spam indicator. | ai |
v0.1.5
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.