@elliemae/microfe-common
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established ICE/Ellie Mae org package; missing gitHead is a CI environment change, not a supply-chain indicator given clean publisher history. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 2.29.2 | 1 / 5 | |
| 2.29.1 | 1 / 5 | |
| 2.29.0 | 1 / 5 | |
| 2.28.8 | 1 / 5 | |
| 2.28.6 | 1 / 5 | |
| 2.28.5 | 1 / 5 | |
| 2.28.4 | 1 / 5 | |
| 2.28.3 | 1 / 5 | |
| 2.28.2 | 1 / 5 | |
| 2.28.1 | 1 / 5 | |
| 2.28.0 | 1 / 5 | |
| 2.27.0 | 1 / 5 | |
| 2.26.0 | 1 / 5 | |
| 2.25.5 | 0 / 5 | |
| 2.25.4 | 0 / 5 | |
| 2.25.3 | 0 / 5 | |
| 2.25.2 | 0 / 4 | |
| 2.25.1 | 0 / 4 | |
| 2.25.0 | 0 / 4 | |
| 2.24.0 | 0 / 4 | |
| 2.23.9 | 0 / 4 | |
| 2.23.8 | 0 / 4 | |
| 2.23.7 | 0 / 4 | |
| 2.23.6 | 0 / 4 | |
| 2.23.4 | 0 / 4 | |
| 2.23.2 | 0 / 4 | |
| 2.23.1 | 0 / 4 | |
| 2.23.0 | 0 / 4 | |
| 2.22.3 | 0 / 4 | |
| 2.22.2 | 0 / 4 | |
| 2.22.1 | 0 / 4 | |
| 2.22.0 | 0 / 4 | |
| 2.21.4 | 0 / 4 | |
| 2.21.3 | 0 / 4 | |
| 2.21.2 | 0 / 5 | |
| 2.21.1 | 0 / 5 | |
| 2.21.0 | 0 / 5 | |
| 2.20.3 | 0 / 5 | |
| 2.20.2 | 0 / 5 | |
| 2.19.2 | 0 / 4 | |
| 2.19.1 | 0 / 4 | |
| 2.19.0 | 0 / 4 | |
| 2.18.1 | 0 / 4 | |
| 2.18.0 | 0 / 4 | |
| 2.17.9 | 0 / 4 | |
| 2.17.8 | 0 / 4 | |
| 2.17.5 | 0 / 4 | |
| 2.17.4 | 0 / 4 | |
| 2.17.3 | 0 / 4 | |
| 2.17.2 | 0 / 4 | |
| 2.17.1 | 0 / 4 | |
| 2.17.0 | 0 / 4 | |
| 2.16.6 | 0 / 4 | |
| 2.16.5 | 0 / 4 | |
| 2.9.11 | 0 / 4 | |
| 2.9.9 | 0 / 4 | |
| 2.9.8 | 0 / 4 | |
| 2.9.4 | 0 / 4 | |
| 2.9.3 | 0 / 4 | |
| 2.9.2 | 0 / 4 | |
| 2.9.1 | 0 / 4 | |
| 2.9.0 | 0 / 4 | |
| 2.8.0 | 0 / 4 | |
| 2.7.8 | 0 / 4 | |
| 2.7.7 | 0 / 4 | |
| 2.7.6 | 0 / 4 | |
| 2.7.5 | 0 / 4 | |
| 2.7.4 | 0 / 4 | |
| 2.7.3 | 0 / 4 | |
| 2.7.2 | 0 / 4 | |
| 2.7.1 | 0 / 4 | |
| 2.7.0 | 0 / 4 | |
| 2.6.6 | 0 / 4 | |
| 2.6.5 | 0 / 4 | |
| 2.6.4 | 0 / 4 | |
| 2.6.3 | 0 / 4 | |
| 2.6.2 | 0 / 4 | |
| 2.6.1 | 0 / 4 | |
| 2.6.0 | 0 / 4 |
v2.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
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.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.