@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, so a manually published version cannot be tied back to a reviewed commit.
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 31 of 31)
| 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 | |
| 0.25.423 | 1 / 0 | |
| 0.25.228 | 1 / 0 | |
| 0.25.226 | 1 / 0 | |
| 0.25.208 | 1 / 0 | |
| 0.25.207 | 1 / 0 | |
| 0.25.122 | 1 / 0 | |
| 0.25.120 | 1 / 0 | |
| 0.25.114 | 1 / 0 | |
| 0.25.112 | 1 / 0 | |
| 0.25.106 | 1 / 0 | |
| 0.24.1218 | 1 / 0 | |
| 0.24.1113 | 1 / 0 | |
| 0.24.1112 | 1 / 0 | |
| 0.24.1002 | 1 / 0 | |
| 0.24.906 | 1 / 0 | |
| 0.24.905 | 1 / 0 | |
| 0.24.904 | 1 / 0 | |
| 0.24.825 | 1 / 0 | |
| 0.24.502 | 1 / 0 | |
| 0.24.501 | 1 / 0 |
v0.25.423
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.228
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.226
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.208
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.207
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.120
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.106
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1218
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.1002
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.906
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.905
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.904
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.825
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.502
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.501
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.