contentstack
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Test tooling addition, not a supply-chain risk. | ai | |
| phantom-deps | phantom-dep:fetch-mock | AI (phantom-deps): Used via config, stable FP. | ai | |
| phantom-deps | phantom-dep:@fetch-mock/jest | AI (phantom-deps): Used via config, stable FP. | ai | |
| dependencies | unvetted-dep:@fetch-mock/jest | AI (dependencies): Legit test-mocking lib matching devDeps additions. | ai | |
| phantom-deps | phantom-dep:qs | AI (phantom-deps): Used via config, stable FP. | ai | |
| dependencies | unvetted-dep:localStorage | AI (dependencies): localStorage 1.0.4 is a standard Node.js localStorage polyfill; expected for a cross-platform JS SDK. | ai | |
| phantom-deps | phantom-dep:husky | AI (phantom-deps): husky is a dev-tool git-hooks package; its presence in dependencies is a packaging quirk, not a security concern. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.27.1 | 4 / 29 | |
| 3.27.0 | 4 / 29 | |
| 3.26.4 | 4 / 29 | |
| 3.26.3 | 4 / 29 | |
| 3.26.2 | 4 / 29 | |
| 3.26.1 | 3 / 22 | |
| 3.25.2 | 6 / 33 | |
| 3.24.3 | 6 / 33 | |
| 3.24.2 | 6 / 33 | |
| 3.24.1 | 5 / 34 | |
| 3.24.0 | 6 / 32 | |
| 3.23.0 | 7 / 32 | |
| 3.22.2 | 7 / 32 | |
| 3.22.1 | 7 / 32 | |
| 3.22.0 | 6 / 32 | |
| 3.21.0 | 6 / 32 | |
| 3.20.3 | 6 / 32 | |
| 3.20.2 | 6 / 32 | |
| 3.20.1 | 6 / 32 | |
| 3.20.0 | 6 / 32 | |
| 3.19.3 | 6 / 32 |
v3.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.