@lemoncloud/ssocio-tenants-api
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established internal API package from lemoncloud org; sparse metadata is typical for org-internal packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; package has 49 versions with no malicious history. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.26.428 | 1 / 0 | |
| 0.26.331 | 1 / 0 | |
| 0.26.330 | 1 / 0 | |
| 0.26.211 | 1 / 0 | |
| 0.25.1201 | 1 / 0 | |
| 0.25.1110 | 1 / 0 | |
| 0.25.1027 | 1 / 0 | |
| 0.25.929 | 1 / 0 | |
| 0.25.620 | 1 / 0 | |
| 0.25.425 | 1 / 0 | |
| 0.25.424 | 1 / 0 |
v0.26.428
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.331
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.330
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.211
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1201
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1110
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1027
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.929
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.620
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.425
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.424
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.