@enonic-types/lib-admin
Type definitions for lib-admin.
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 | new-deps-added | AI (publish-pattern): Same-org sibling package pinned to identical version; not a supply-chain risk. | ai | |
| provenance | missing-githead | AI (provenance): CI-published with SLSA attestation; gitHead omission is metadata noise, not a regression. | ai | |
| phantom-deps | phantom-dep:@enonic-types/core | AI (phantom-deps): Pure TypeScript type definitions package; deps are type-only and won't appear as runtime imports. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 8.0.3 | 1 / 0 | |
| 8.0.2 | 1 / 0 | |
| 8.0.1 | 1 / 0 | |
| 8.0.0 | 1 / 0 | |
| 7.16.7 | 0 / 0 | |
| 7.16.6 | 0 / 0 | |
| 7.16.5 | 0 / 0 | |
| 7.16.4 | 0 / 0 | |
| 7.16.3 | 0 / 0 | |
| 7.16.2 | 0 / 0 | |
| 7.16.1 | 0 / 0 | |
| 7.16.0 | 0 / 0 | |
| 7.15.4 | 0 / 0 | |
| 7.15.3 | 0 / 0 | |
| 7.15.2 | 0 / 0 | |
| 7.15.1 | 0 / 0 | |
| 7.15.0 | 0 / 0 | |
| 7.14.4 | 0 / 0 | |
| 7.14.3 | 0 / 0 | |
| 7.14.2 | 0 / 0 |
v8.0.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.