@contentstack/cli-cm-seed
create a Stack from existing content types, entries, assets, etc.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Contentstack CLI packages consistently publish without Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 1.15.8 | 7 / 14 | |
| 1.15.7 | 7 / 14 | |
| 1.15.6 | 7 / 14 | |
| 1.15.5 | 7 / 14 | |
| 1.15.4 | 7 / 14 | |
| 1.15.3 | 7 / 14 | |
| 1.15.2 | 7 / 14 | |
| 1.15.1 | 7 / 15 | |
| 1.15.0 | 7 / 15 | |
| 1.14.3 | 7 / 15 | |
| 1.14.2 | 8 / 15 | |
| 1.14.1 | 8 / 15 | |
| 1.14.0 | 8 / 15 | |
| 1.13.2 | 8 / 15 | |
| 1.13.1 | 8 / 15 | |
| 1.13.0 | 8 / 15 | |
| 1.12.2 | 8 / 15 | |
| 1.12.1 | 8 / 15 | |
| 1.12.0 | 8 / 15 | |
| 1.11.3 | 8 / 15 | |
| 1.11.2 | 8 / 15 | |
| 1.11.1 | 8 / 15 | |
| 1.11.0 | 8 / 15 | |
| 1.10.3 | 8 / 15 | |
| 1.10.2 | 8 / 15 | |
| 1.10.1 | 8 / 15 | |
| 1.10.0 | 8 / 17 | |
| 1.9.0 | 8 / 17 | |
| 1.8.0 | 8 / 17 | |
| 1.7.8 | 8 / 17 | |
| 1.7.7 | 8 / 17 | |
| 1.7.6 | 8 / 17 | |
| 1.7.5 | 8 / 17 | |
| 1.7.4 | 8 / 17 |
v1.15.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
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.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.