@contentstack/core
[](https://www.contentstack.com/)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package under official contentstack org; not a typosquat of cors. | ai | |
| phantom-deps | phantom-dep:axios-mock-adapter | AI (phantom-deps): axios-mock-adapter is a test utility; phantom-dep heuristic fires as false positive here. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 5 / 37 | |
| 1.4.0 | 5 / 37 | |
| 1.3.14 | 5 / 37 | |
| 1.3.13 | 5 / 37 | |
| 1.3.12 | 5 / 37 | |
| 1.3.11 | 5 / 37 | |
| 1.3.10 | 5 / 37 | |
| 1.3.9 | 5 / 37 | |
| 1.3.8 | 6 / 37 | |
| 1.3.7 | 6 / 37 | |
| 1.3.6 | 6 / 37 | |
| 1.3.5 | 6 / 37 | |
| 1.3.4 | 6 / 37 | |
| 1.3.3 | 6 / 37 | |
| 1.3.2 | 6 / 37 | |
| 1.3.1 | 6 / 37 | |
| 1.3.0 | 6 / 37 | |
| 1.2.4 | 6 / 37 | |
| 1.2.3 | 6 / 37 | |
| 1.2.2 | 5 / 37 | |
| 1.2.1 | 5 / 37 | |
| 1.2.0 | 5 / 37 | |
| 1.1.4 | 5 / 37 | |
| 1.1.3 | 5 / 37 | |
| 1.1.2 | 5 / 37 | |
| 1.1.1 | 5 / 37 | |
| 1.1.0 | 5 / 37 | |
| 1.0.3 | 5 / 37 |
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.