@marianmeres/collection-types
Type definitions and schema utilities for the @marianmeres/collection ecosystem.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher with clean track record; missing gitHead is a minor CI environment change, not a malware indicator. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established scoped package with 43 versions and real downloads; sparse metadata is a style choice, not spam. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 2.12.0 | 0 / 0 | |
| 2.11.0 | 0 / 0 | |
| 2.10.0 | 0 / 0 | |
| 2.9.0 | 0 / 0 | |
| 2.8.0 | 0 / 0 | |
| 2.6.0 | 0 / 0 | |
| 2.5.0 | 0 / 0 | |
| 2.4.0 | 0 / 0 | |
| 2.3.0 | 0 / 0 | |
| 2.2.0 | 0 / 0 | |
| 2.1.0 | 0 / 0 | |
| 2.0.0 | 0 / 0 | |
| 1.41.0 | 0 / 0 | |
| 1.40.0 | 0 / 0 | |
| 1.39.0 | 0 / 0 | |
| 1.38.1 | 0 / 0 | |
| 1.38.0 | 0 / 0 | |
| 1.37.0 | 0 / 0 | |
| 1.36.0 | 0 / 0 | |
| 1.35.0 | 0 / 0 | |
| 1.34.0 | 0 / 0 | |
| 1.33.1 | 0 / 0 | |
| 1.33.0 | 0 / 0 | |
| 1.32.0 | 0 / 0 | |
| 1.31.0 | 0 / 0 | |
| 1.30.0 | 0 / 0 | |
| 1.29.0 | 0 / 0 | |
| 1.28.0 | 0 / 0 | |
| 1.26.0 | 0 / 0 | |
| 1.25.0 | 0 / 0 | |
| 1.24.0 | 0 / 0 | |
| 1.23.0 | 0 / 0 | |
| 1.22.0 | 0 / 0 | |
| 1.21.0 | 0 / 0 | |
| 1.20.0 | 0 / 0 | |
| 1.19.0 | 0 / 0 | |
| 1.18.0 | 0 / 0 | |
| 1.17.0 | 0 / 0 | |
| 1.16.0 | 0 / 0 | |
| 1.15.0 | 0 / 0 | |
| 1.14.0 | 0 / 0 | |
| 1.13.0 | 0 / 0 | |
| 1.12.0 | 0 / 0 | |
| 1.11.0 | 0 / 0 | |
| 1.10.0 | 0 / 0 | |
| 1.9.0 | 0 / 0 | |
| 1.8.1 | 0 / 0 | |
| 1.8.0 | 0 / 0 | |
| 1.7.0 | 0 / 0 | |
| 1.6.1 | 0 / 0 | |
| 1.6.0 | 0 / 0 | |
| 1.5.0 | 0 / 0 | |
| 1.4.0 | 0 / 0 | |
| 1.3.0 | 0 / 0 | |
| 1.2.0 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.1 | 0 / 0 |
v2.12.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marianmeres.
v2.11.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marianmeres.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marianmeres.
v2.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marianmeres.
v2.6.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: marianmeres.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.