@adobe/aep-rules-engine
4
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
marbectripodgarthdblazdadobe-adminpatrickfultontrieloffkrisnyedcpfsdknatebaldwindevongovettaspro83symanovidpfisterstefan-guggisbergrofekptdobeadobehallsfullcolorcoderdjaeggidylandepassmhaackamol-anandstopp-adobenamaroradotenduh_schmidtasthabh23zdahbituicufmeschbe
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): Adobe org team rotation on official scoped package, no malicious behavior evident. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with team rotation, not a takeover pattern given publisher trust. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Low-velocity official SDK; dormancy alone not indicative of compromise. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.1.2 | 0 / 28 | |
| 3.1.1 | 1 / 27 | |
| 3.1.0 | 1 / 27 | |
| 3.0.0 | 1 / 27 |
v3.1.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.