@stacksjs/cloud
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo publishes many packages in lockstep quickly; normal cadence for stacksjs. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Registry import artifact, not real dormancy; steady npm publish history for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@stacksjs/dns | AI (phantom-deps): Same-org sibling loaded by framework convention. | ai | |
| dependencies | unvetted-dep:@stacksjs/validation | AI (dependencies): First-party sibling package within same monorepo/org. | ai | |
| dependencies | unvetted-dep:@stacksjs/dns | AI (dependencies): First-party sibling package within same monorepo/org. | ai | |
| phantom-deps | phantom-dep:aws-cdk | AI (phantom-deps): CDK config-referenced, not imported; expected for CDK tooling. | ai | |
| dependencies | unvetted-dep:@stacksjs/ts-xml | AI (dependencies): Same-org first-party dependency within the stacksjs monorepo. | ai | |
| phantom-deps | phantom-dep:@stacksjs/ts-xml | AI (phantom-deps): Same org scope, likely re-exported internally. | ai |
Versions (showing 51 of 74)
| Version | Deps | Published |
|---|---|---|
| 0.70.170 | 2 / 11 | |
| 0.70.139 | 2 / 11 | |
| 0.70.115 | 2 / 11 | |
| 0.70.93 | 2 / 11 | |
| 0.70.84 | 2 / 11 | |
| 0.70.79 | 2 / 11 | |
| 0.70.76 | 2 / 11 | |
| 0.70.75 | 1 / 11 | |
| 0.70.74 | 1 / 11 | |
| 0.70.73 | 1 / 11 | |
| 0.70.72 | 1 / 11 | |
| 0.70.71 | 1 / 11 | |
| 0.70.70 | 1 / 11 | |
| 0.70.69 | 1 / 11 | |
| 0.70.68 | 1 / 11 | |
| 0.70.67 | 1 / 11 | |
| 0.70.66 | 1 / 11 | |
| 0.70.65 | 1 / 11 | |
| 0.70.64 | 1 / 11 | |
| 0.70.63 | 1 / 11 | |
| 0.70.62 | 1 / 11 | |
| 0.70.61 | 1 / 11 | |
| 0.70.60 | 1 / 11 | |
| 0.70.59 | 1 / 11 | |
| 0.70.58 | 1 / 11 | |
| 0.70.57 | 1 / 11 | |
| 0.70.56 | 1 / 11 | |
| 0.70.55 | 1 / 11 | |
| 0.70.54 | 1 / 11 | |
| 0.70.53 | 1 / 11 | |
| 0.70.45 | 1 / 11 | |
| 0.70.44 | 1 / 11 | |
| 0.70.43 | 1 / 11 | |
| 0.70.42 | 1 / 11 | |
| 0.70.37 | 1 / 11 | |
| 0.70.36 | 1 / 11 | |
| 0.70.35 | 1 / 11 | |
| 0.70.34 | 1 / 11 | |
| 0.70.33 | 1 / 11 | |
| 0.70.32 | 1 / 11 | |
| 0.70.31 | 1 / 11 | |
| 0.70.30 | 1 / 11 | |
| 0.70.29 | 1 / 11 | |
| 0.70.28 | 1 / 11 | |
| 0.70.27 | 1 / 11 | |
| 0.70.26 | 1 / 11 | |
| 0.70.25 | 1 / 11 | |
| 0.70.23 | 0 / 30 | |
| 0.70.22 | 0 / 30 | |
| 0.70.21 | 0 / 30 | |
| 0.70.19 | 0 / 30 |
v0.70.170
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.139
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.115
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.93
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.84
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.79
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.76
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.75
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.74
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.73
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.72
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.71
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.70
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.69
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.68
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.67
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.66
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.65
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.64
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.63
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.62
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.61
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.60
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.59
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.58
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.57
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.56
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.55
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.54
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.53
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.70.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.70.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.