@adobe/spacecat-shared-utils
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Adobe org migrated publishing to GitHub Actions CI/CD; SLSA provenance attestation confirms supply chain integrity. | ai | |
| dependencies | unvetted-dep:@adobe/spacecat-shared-ims-client | AI (dependencies): First-party Adobe/spacecat package from the same org and publisher lineage. | ai | |
| dependencies | unvetted-dep:aws-xray-sdk | AI (dependencies): aws-xray-sdk is an official AWS observability SDK; no malware indicators, stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@json2csv/plainjs | AI (dependencies): @json2csv/plainjs is a well-known CSV conversion library; no malware indicators, stable dependency for this package. | ai |
Versions (showing 100 of 233)
| Version | Deps | Published |
|---|---|---|
| 1.70.1 | 12 / 9 | |
| 1.70.0 | 12 / 9 | |
| 1.69.4 | 12 / 9 | |
| 1.69.3 | 12 / 9 | |
| 1.69.2 | 12 / 9 | |
| 1.69.1 | 12 / 9 | |
| 1.69.0 | 12 / 9 | |
| 1.68.0 | 12 / 9 | |
| 1.67.0 | 12 / 9 | |
| 1.66.1 | 12 / 9 | |
| 1.66.0 | 14 / 9 | |
| 1.65.0 | 15 / 9 | |
| 1.64.0 | 15 / 9 | |
| 1.63.0 | 15 / 9 | |
| 1.62.0 | 15 / 9 | |
| 1.61.0 | 15 / 9 | |
| 1.60.0 | 15 / 9 | |
| 1.59.4 | 15 / 9 | |
| 1.59.3 | 15 / 9 | |
| 1.59.2 | 15 / 9 | |
| 1.59.1 | 15 / 9 | |
| 1.59.0 | 15 / 9 | |
| 1.58.1 | 11 / 9 | |
| 1.58.0 | 11 / 9 | |
| 1.57.1 | 11 / 9 | |
| 1.57.0 | 11 / 9 | |
| 1.56.0 | 11 / 9 | |
| 1.55.0 | 11 / 9 | |
| 1.54.0 | 11 / 9 | |
| 1.53.0 | 11 / 9 | |
| 1.52.0 | 11 / 9 | |
| 1.51.1 | 11 / 9 | |
| 1.51.0 | 11 / 9 | |
| 1.50.8 | 10 / 9 | |
| 1.50.7 | 10 / 9 | |
| 1.50.6 | 10 / 9 | |
| 1.50.5 | 10 / 9 | |
| 1.50.4 | 10 / 9 | |
| 1.50.3 | 10 / 9 | |
| 1.50.2 | 11 / 9 | |
| 1.50.1 | 11 / 9 | |
| 1.50.0 | 11 / 9 | |
| 1.49.0 | 10 / 8 | |
| 1.48.0 | 10 / 8 | |
| 1.47.0 | 10 / 8 | |
| 1.46.0 | 9 / 8 | |
| 1.45.0 | 9 / 8 | |
| 1.44.3 | 9 / 8 | |
| 1.44.2 | 9 / 8 | |
| 1.44.1 | 9 / 8 | |
| 1.44.0 | 9 / 8 | |
| 1.43.1 | 9 / 8 | |
| 1.43.0 | 9 / 8 | |
| 1.42.4 | 9 / 8 | |
| 1.42.3 | 9 / 8 | |
| 1.42.2 | 9 / 8 | |
| 1.42.1 | 9 / 8 | |
| 1.42.0 | 9 / 8 | |
| 1.41.3 | 9 / 8 | |
| 1.41.2 | 9 / 8 | |
| 1.41.1 | 7 / 9 | |
| 1.41.0 | 7 / 9 | |
| 1.40.0 | 7 / 9 | |
| 1.39.1 | 7 / 9 | |
| 1.39.0 | 7 / 9 | |
| 1.38.6 | 7 / 9 | |
| 1.38.5 | 7 / 9 | |
| 1.38.4 | 7 / 9 | |
| 1.38.3 | 7 / 9 | |
| 1.38.2 | 7 / 9 | |
| 1.38.1 | 7 / 9 | |
| 1.38.0 | 7 / 9 | |
| 1.37.4 | 6 / 9 | |
| 1.37.3 | 6 / 9 | |
| 1.37.2 | 6 / 9 | |
| 1.37.1 | 6 / 9 | |
| 1.37.0 | 6 / 9 | |
| 1.36.3 | 6 / 8 | |
| 1.36.2 | 6 / 8 | |
| 1.36.1 | 6 / 8 | |
| 1.36.0 | 6 / 8 | |
| 1.35.2 | 6 / 8 | |
| 1.35.1 | 6 / 8 | |
| 1.35.0 | 6 / 8 | |
| 1.34.0 | 6 / 8 | |
| 1.33.3 | 6 / 8 | |
| 1.33.2 | 6 / 8 | |
| 1.33.1 | 6 / 8 | |
| 1.33.0 | 6 / 8 | |
| 1.32.0 | 6 / 8 | |
| 1.31.1 | 6 / 8 | |
| 1.31.0 | 6 / 8 | |
| 1.30.4 | 6 / 8 | |
| 1.30.3 | 6 / 8 | |
| 1.30.2 | 7 / 8 | |
| 1.30.1 | 7 / 8 | |
| 1.30.0 | 7 / 8 | |
| 1.29.0 | 7 / 8 | |
| 1.28.4 | 7 / 8 | |
| 1.28.3 | 7 / 8 |
v1.69.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.41.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.