@contractspec/bundle.lifecycle-managed
Lifecycle management bundle with analytics and AI advisor
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@contractspec/lib.analytics | AI (phantom-deps): Same-org bundle; dep likely re-exported rather than directly imported in this package. | ai | |
| phantom-deps | phantom-dep:@contractspec/lib.surface-runtime | AI (phantom-deps): Same-org bundle; dep likely re-exported rather than directly imported in this package. | ai |
Versions (showing 81 of 81)
| Version | Deps | Published |
|---|---|---|
| 3.7.29 | 7 / 3 | |
| 3.7.28 | 7 / 3 | |
| 3.7.27 | 7 / 3 | |
| 3.7.26 | 7 / 3 | |
| 3.7.25 | 7 / 3 | |
| 3.7.24 | 7 / 3 | |
| 3.7.23 | 7 / 3 | |
| 3.7.22 | 7 / 3 | |
| 3.7.21 | 7 / 3 | |
| 3.7.20 | 6 / 3 | |
| 3.7.19 | 6 / 3 | |
| 3.7.18 | 6 / 3 | |
| 3.7.17 | 6 / 3 | |
| 3.7.16 | 6 / 3 | |
| 3.7.15 | 6 / 3 | |
| 3.7.14 | 6 / 3 | |
| 3.7.12 | 6 / 3 | |
| 3.7.10 | 6 / 3 | |
| 3.7.7 | 6 / 3 | |
| 3.7.6 | 6 / 3 | |
| 3.7.5 | 6 / 3 | |
| 3.7.4 | 6 / 3 | |
| 3.7.3 | 6 / 3 | |
| 3.7.1 | 6 / 3 | |
| 3.7.0 | 6 / 3 | |
| 3.6.0 | 6 / 3 | |
| 3.5.5 | 6 / 3 | |
| 3.5.4 | 6 / 3 | |
| 3.5.3 | 6 / 3 | |
| 3.5.2 | 6 / 3 | |
| 3.5.0 | 6 / 3 | |
| 3.4.3 | 6 / 3 | |
| 3.4.2 | 6 / 3 | |
| 3.4.1 | 6 / 3 | |
| 3.4.0 | 6 / 3 | |
| 3.3.0 | 6 / 3 | |
| 3.2.0 | 6 / 3 | |
| 3.1.1 | 6 / 3 | |
| 3.0.0 | 6 / 3 | |
| 2.9.1 | 6 / 3 | |
| 2.9.0 | 6 / 3 | |
| 2.8.0 | 6 / 3 | |
| 2.7.0 | 6 / 3 | |
| 2.6.0 | 6 / 3 | |
| 2.5.0 | 6 / 3 | |
| 2.4.0 | 6 / 3 | |
| 2.3.0 | 6 / 3 | |
| 2.2.0 | 6 / 3 | |
| 2.1.1 | 6 / 3 | |
| 2.1.0 | 6 / 3 | |
| 2.0.0 | 6 / 3 | |
| 1.62.0 | 6 / 3 | |
| 1.61.0 | 6 / 3 | |
| 1.60.0 | 6 / 3 | |
| 1.59.0 | 6 / 3 | |
| 1.58.0 | 6 / 3 | |
| 1.57.0 | 6 / 4 | |
| 1.56.1 | 6 / 4 | |
| 1.56.0 | 6 / 4 | |
| 1.55.0 | 6 / 4 | |
| 1.54.0 | 6 / 4 | |
| 1.53.0 | 6 / 4 | |
| 1.52.0 | 6 / 4 | |
| 1.51.0 | 6 / 4 | |
| 1.50.0 | 6 / 4 | |
| 1.49.0 | 6 / 4 | |
| 1.48.1 | 6 / 4 | |
| 1.48.0 | 6 / 4 | |
| 1.47.0 | 6 / 4 | |
| 1.46.2 | 6 / 4 | |
| 1.46.1 | 6 / 4 | |
| 1.46.0 | 6 / 4 | |
| 1.45.6 | 6 / 4 | |
| 1.45.5 | 6 / 4 | |
| 1.45.4 | 6 / 4 | |
| 1.45.3 | 6 / 4 | |
| 1.45.2 | 6 / 4 | |
| 1.45.1 | 6 / 4 | |
| 1.45.0 | 6 / 4 | |
| 1.44.1 | 6 / 4 | |
| 1.44.0 | 6 / 4 |
v3.7.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.59.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.