@macrostrat/feedback-components
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 component; sparse README/metadata is expected for org-scoped packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-scoped monorepo package; missing description is a stable non-issue here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.2.3 | 13 / 1 | |
| 2.2.2 | 13 / 1 | |
| 2.2.1 | 13 / 1 | |
| 2.2.0 | 13 / 1 | |
| 2.1.4 | 13 / 1 | |
| 2.1.3 | 13 / 1 | |
| 2.1.2 | 13 / 1 | |
| 2.1.1 | 13 / 1 | |
| 2.1.0 | 13 / 1 | |
| 2.0.3 | 13 / 1 | |
| 2.0.2 | 13 / 1 | |
| 2.0.1 | 13 / 1 | |
| 2.0.0 | 13 / 1 | |
| 1.1.10 | 15 / 1 |
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.