@contractspec/example.learning-journey-registry
Registry that aggregates learning journey example tracks.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/browser/ui/presentation-data.js | AI (source-diff): Standard Bun-bundled minified ESM output; readable imports and domain logic, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/node/ui/presentation-data.js | AI (source-diff): Standard Bun-bundled minified ESM output; readable imports and domain logic, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/ui/presentation-data.js | AI (source-diff): Standard Bun-bundled minified ESM output; readable imports and domain logic, not malicious obfuscation. | ai | |
| dependencies | unvetted-dep:@contractspec/example.learning-journey-ui-coaching | AI (dependencies): Same-org monorepo sibling dep; coordinated versioning is expected for this package. | ai | |
| dependencies | unvetted-dep:@contractspec/example.learning-journey-ui-gamified | AI (dependencies): Same-org monorepo sibling dep; coordinated versioning is expected for this package. | ai | |
| dependencies | unvetted-dep:@contractspec/example.learning-journey-ui-onboarding | AI (dependencies): Same-org monorepo sibling dep; coordinated versioning is expected for this package. | ai |
Versions (showing 51 of 83)
| Version | Deps | Published |
|---|---|---|
| 4.0.13 | 14 / 4 | |
| 4.0.12 | 14 / 4 | |
| 4.0.11 | 14 / 4 | |
| 4.0.10 | 14 / 4 | |
| 4.0.9 | 14 / 4 | |
| 4.0.8 | 13 / 4 | |
| 4.0.7 | 13 / 4 | |
| 4.0.6 | 13 / 4 | |
| 4.0.5 | 13 / 4 | |
| 4.0.4 | 13 / 4 | |
| 4.0.3 | 13 / 4 | |
| 4.0.2 | 13 / 4 | |
| 4.0.0 | 13 / 4 | |
| 3.7.19 | 13 / 4 | |
| 3.7.18 | 13 / 4 | |
| 3.7.17 | 13 / 4 | |
| 3.7.16 | 13 / 4 | |
| 3.7.15 | 13 / 4 | |
| 3.7.14 | 13 / 4 | |
| 3.7.12 | 13 / 4 | |
| 3.7.10 | 13 / 4 | |
| 3.7.7 | 13 / 4 | |
| 3.7.6 | 13 / 4 | |
| 3.7.5 | 13 / 4 | |
| 3.7.4 | 13 / 4 | |
| 3.7.3 | 13 / 4 | |
| 3.7.1 | 13 / 4 | |
| 3.7.0 | 13 / 4 | |
| 3.6.0 | 13 / 4 | |
| 3.5.5 | 13 / 4 | |
| 3.5.4 | 13 / 4 | |
| 3.5.3 | 13 / 4 | |
| 3.5.2 | 13 / 4 | |
| 3.5.0 | 13 / 4 | |
| 3.4.3 | 13 / 4 | |
| 3.4.2 | 13 / 4 | |
| 3.4.1 | 13 / 4 | |
| 3.4.0 | 13 / 4 | |
| 3.3.0 | 13 / 4 | |
| 3.2.0 | 13 / 4 | |
| 3.1.1 | 13 / 4 | |
| 3.0.0 | 13 / 4 | |
| 2.9.1 | 13 / 4 | |
| 2.9.0 | 13 / 4 | |
| 2.8.0 | 13 / 4 | |
| 2.7.0 | 13 / 4 | |
| 2.6.1 | 13 / 4 | |
| 2.6.0 | 13 / 4 | |
| 2.5.0 | 13 / 4 | |
| 2.4.0 | 13 / 4 | |
| 2.3.0 | 13 / 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.