jsuites
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@jsuites/utils | AI (phantom-deps): Bundled package; referenced in build config, not directly imported in source — expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/tabs | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/color | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/modal | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/rating | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/switch | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/topmenu | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/calendar | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/dropdown | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@lemonadejs/contextmenu | AI (phantom-deps): Same bundled/config-reference pattern; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 6.4.0 | 10 / 18 | |
| 6.3.6 | 10 / 18 | |
| 6.3.5 | 10 / 18 | |
| 6.3.4 | 10 / 18 | |
| 6.3.3 | 10 / 18 | |
| 6.3.2 | 10 / 18 | |
| 6.3.1 | 10 / 18 | |
| 6.3.0 | 10 / 18 | |
| 6.2.1 | 10 / 18 | |
| 6.2.0 | 10 / 18 | |
| 6.1.3 | 10 / 18 | |
| 6.1.2 | 10 / 18 | |
| 6.1.1 | 10 / 18 | |
| 6.1.0 | 10 / 18 | |
| 6.0.3 | 10 / 18 | |
| 6.0.1 | 10 / 18 | |
| 6.0.0 | 10 / 18 | |
| 5.13.5 | 0 / 17 |
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.