@embroider/macros
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from ef4 to GitHub Actions is consistent with CI/CD automation; SLSA provenance attestation confirms integrity. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by CI/CD-attested publish in an established monorepo package; no malicious indicators. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Used to load ember-source package.json for version detection at build time; not user-controlled arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:ember-cli-babel | AI (phantom-deps): ember-cli-babel is a legitimate runtime dep used via config/build tooling, not direct import; stable false positive for this package. | ai |
Versions (showing 51 of 66)
| Version | Deps | Published |
|---|---|---|
| 1.20.5 | 8 / 20 | |
| 1.20.4 | 8 / 20 | |
| 1.20.3 | 8 / 20 | |
| 1.20.2 | 8 / 20 | |
| 1.20.1 | 8 / 20 | |
| 1.20.0 | 8 / 20 | |
| 1.19.7 | 8 / 20 | |
| 1.19.6 | 8 / 20 | |
| 1.19.5 | 8 / 20 | |
| 1.19.4 | 8 / 20 | |
| 1.19.3 | 8 / 20 | |
| 1.19.2 | 8 / 20 | |
| 1.19.1 | 8 / 20 | |
| 1.19.0 | 8 / 20 | |
| 1.18.3 | 8 / 19 | |
| 1.18.2 | 8 / 18 | |
| 1.18.1 | 8 / 18 | |
| 1.18.0 | 8 / 18 | |
| 1.17.3 | 8 / 18 | |
| 1.17.2 | 8 / 18 | |
| 1.17.1 | 8 / 18 | |
| 1.17.0 | 8 / 18 | |
| 1.16.13 | 8 / 18 | |
| 1.16.12 | 8 / 18 | |
| 1.16.11 | 8 / 18 | |
| 1.16.10 | 8 / 18 | |
| 1.16.9 | 8 / 18 | |
| 1.16.8 | 8 / 18 | |
| 1.16.7 | 8 / 18 | |
| 1.16.6 | 8 / 18 | |
| 1.16.5 | 8 / 18 | |
| 1.16.4 | 8 / 18 | |
| 1.16.3 | 8 / 18 | |
| 1.16.2 | 8 / 18 | |
| 1.16.1 | 8 / 18 | |
| 1.16.0 | 9 / 17 | |
| 1.15.1 | 9 / 17 | |
| 1.15.0 | 9 / 17 | |
| 1.14.0 | 8 / 18 | |
| 1.13.5 | 8 / 18 | |
| 1.13.4 | 8 / 18 | |
| 1.13.3 | 8 / 18 | |
| 1.13.2 | 8 / 18 | |
| 1.13.1 | 8 / 18 | |
| 1.13.0 | 8 / 18 | |
| 1.12.3 | 8 / 18 | |
| 1.12.2 | 8 / 18 | |
| 1.12.1 | 8 / 18 | |
| 1.12.0 | 8 / 18 | |
| 1.11.1 | 8 / 18 | |
| 1.11.0 | 8 / 18 |
v1.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.16.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (real_ate) than the most recent previously approved version (ef4) on 2023-12-13, but real_ate is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nullvoxpopuli) than the most recent previously approved version (ef4) on 2023-07-21, but nullvoxpopuli is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.