@bpinternal/shared
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): Internal monorepo shared lib; missing metadata is expected for private/internal packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal scoped package from Botpress org; missing description is cosmetic, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions; no provenance is common and not a risk indicator for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.2.5 | 3 / 9 | |
| 1.2.4 | 3 / 9 | |
| 1.2.3 | 3 / 9 | |
| 1.2.2 | 3 / 9 | |
| 1.2.1 | 3 / 9 | |
| 1.2.0 | 3 / 9 | |
| 1.1.13 | 3 / 9 | |
| 1.1.12 | 3 / 9 | |
| 1.1.11 | 3 / 9 | |
| 1.1.8 | 3 / 9 | |
| 1.1.7 | 3 / 9 | |
| 1.1.6 | 3 / 9 | |
| 1.1.5 | 3 / 9 | |
| 1.1.3 | 3 / 9 | |
| 1.1.2 | 3 / 9 | |
| 1.1.0 | 3 / 9 | |
| 1.0.3 | 3 / 9 | |
| 1.0.2 | 3 / 9 | |
| 1.0.1 | 3 / 7 | |
| 1.0.0 | 3 / 7 |
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.