@assaabloy/amarr-wc-dealer-leads-program
Web component - Dealer-leads-program
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): No behavioral change in diff; likely internal org handoff for enterprise-scoped package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy with unchanged code/scripts, consistent with low-cadence internal component. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 9.6.1 | 0 / 0 | |
| 9.6.0 | 0 / 0 | |
| 9.5.14 | 0 / 0 | |
| 9.5.13 | 0 / 0 | |
| 9.5.12 | 0 / 0 | |
| 9.5.11 | 0 / 0 | |
| 9.5.10 | 0 / 0 | |
| 9.5.9 | 0 / 0 | |
| 9.5.7 | 0 / 0 | |
| 9.5.5 | 0 / 0 | |
| 9.5.4 | 0 / 0 | |
| 9.5.3 | 0 / 0 | |
| 9.5.2 | 0 / 0 | |
| 9.5.1 | 0 / 0 | |
| 9.5.0 | 0 / 0 | |
| 9.4.3 | 0 / 0 | |
| 9.4.2 | 0 / 0 | |
| 9.4.1 | 0 / 0 | |
| 9.4.0 | 0 / 0 | |
| 9.3.23 | 0 / 0 | |
| 9.3.22 | 0 / 0 | |
| 9.3.21 | 0 / 0 | |
| 9.3.20 | 0 / 0 | |
| 9.3.19 | 0 / 0 | |
| 9.3.18 | 0 / 0 | |
| 9.3.17 | 0 / 0 | |
| 9.3.16 | 0 / 0 | |
| 9.3.15 | 0 / 0 | |
| 9.3.14 | 0 / 0 | |
| 9.3.13 | 0 / 0 | |
| 9.3.12 | 0 / 0 | |
| 9.3.11 | 0 / 0 | |
| 9.3.10 | 0 / 0 | |
| 9.3.9 | 0 / 0 | |
| 9.3.8 | 0 / 0 | |
| 9.3.7 | 0 / 0 | |
| 9.3.6 | 0 / 0 | |
| 9.3.5 | 0 / 0 | |
| 9.3.4 | 0 / 0 | |
| 9.3.3 | 0 / 0 | |
| 9.3.2 | 0 / 0 | |
| 9.3.1 | 0 / 0 | |
| 9.3.0 | 0 / 0 | |
| 9.2.56 | 0 / 0 | |
| 9.2.55 | 0 / 0 | |
| 9.2.54 | 0 / 0 | |
| 9.2.53 | 0 / 0 | |
| 9.2.52 | 0 / 0 | |
| 9.2.51 | 0 / 0 | |
| 9.2.48 | 0 / 0 |
v9.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.2.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.