@contractspec/example.learning-journey-ui-onboarding
Developer onboarding UI with checklists and journey maps.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@contractspec/example.learning-journey-platform-tour | AI (phantom-deps): Same-org package declared as dep but may be used indirectly; consistent pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@contractspec/example.learning-journey-studio-onboarding | AI (phantom-deps): Same-org package declared as dep but may be used indirectly; consistent pattern across this monorepo. | ai |
Versions (showing 51 of 84)
| Version | Deps | Published |
|---|---|---|
| 4.0.13 | 9 / 4 | |
| 4.0.12 | 9 / 4 | |
| 4.0.11 | 9 / 4 | |
| 4.0.10 | 9 / 4 | |
| 4.0.9 | 9 / 4 | |
| 4.0.8 | 9 / 4 | |
| 4.0.7 | 9 / 4 | |
| 4.0.6 | 9 / 4 | |
| 4.0.5 | 9 / 4 | |
| 4.0.4 | 9 / 4 | |
| 4.0.3 | 9 / 4 | |
| 4.0.2 | 9 / 4 | |
| 4.0.0 | 9 / 4 | |
| 3.7.19 | 9 / 4 | |
| 3.7.18 | 9 / 4 | |
| 3.7.17 | 9 / 4 | |
| 3.7.16 | 9 / 4 | |
| 3.7.15 | 9 / 4 | |
| 3.7.14 | 9 / 4 | |
| 3.7.12 | 9 / 4 | |
| 3.7.10 | 9 / 4 | |
| 3.7.7 | 9 / 4 | |
| 3.7.6 | 9 / 4 | |
| 3.7.5 | 9 / 4 | |
| 3.7.4 | 9 / 4 | |
| 3.7.3 | 9 / 4 | |
| 3.7.1 | 9 / 4 | |
| 3.7.0 | 9 / 4 | |
| 3.6.0 | 9 / 4 | |
| 3.5.5 | 9 / 4 | |
| 3.5.4 | 9 / 4 | |
| 3.5.3 | 9 / 4 | |
| 3.5.2 | 9 / 4 | |
| 3.5.0 | 9 / 4 | |
| 3.4.3 | 9 / 4 | |
| 3.4.2 | 9 / 4 | |
| 3.4.1 | 9 / 4 | |
| 3.4.0 | 9 / 4 | |
| 3.3.0 | 9 / 4 | |
| 3.2.0 | 9 / 4 | |
| 3.1.1 | 9 / 4 | |
| 3.0.0 | 9 / 4 | |
| 2.9.1 | 9 / 4 | |
| 2.9.0 | 9 / 4 | |
| 2.8.0 | 9 / 4 | |
| 2.7.0 | 9 / 4 | |
| 2.6.1 | 9 / 4 | |
| 2.6.0 | 9 / 4 | |
| 2.5.0 | 9 / 4 | |
| 2.4.0 | 9 / 4 | |
| 2.3.0 | 9 / 4 |
v4.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.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.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.1
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.