@contentstack/utils
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 |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall fetches a static JSON file from Contentstack's own CDN with a safe fallback; stable pattern for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 0 / 26 | |
| 1.9.0 | 0 / 26 | |
| 1.8.0 | 0 / 26 | |
| 1.7.1 | 0 / 26 | |
| 1.7.0 | 0 / 26 | |
| 1.6.3 | 0 / 26 | |
| 1.6.2 | 0 / 26 | |
| 1.6.0 | 0 / 24 | |
| 1.5.0 | 0 / 24 | |
| 1.4.4 | 0 / 24 | |
| 1.4.3 | 0 / 29 | |
| 1.4.2 | 0 / 29 | |
| 1.4.1 | 0 / 29 | |
| 1.4.0 | 0 / 29 | |
| 1.3.20 | 0 / 29 | |
| 1.3.19 | 0 / 29 | |
| 1.3.18 | 0 / 29 | |
| 1.3.17 | 0 / 29 | |
| 1.3.16 | 0 / 29 | |
| 1.3.15 | 0 / 29 | |
| 1.3.14 | 0 / 29 | |
| 1.3.13 | 0 / 29 | |
| 1.3.12 | 0 / 29 | |
| 1.3.11 | 0 / 29 | |
| 1.3.10 | 0 / 29 | |
| 1.3.9 | 0 / 29 | |
| 1.3.8 | 0 / 29 | |
| 1.3.7 | 0 / 29 | |
| 1.3.6 | 2 / 30 | |
| 1.3.5 | 2 / 30 | |
| 1.3.4 | 2 / 30 |
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.