react-animate-height
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Same rationale; stale non-suspicious publisher change. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Known maintainer by email, long-stable publish; not a takeover. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 3.2.4 | 0 / 8 | |
| 3.2.3 | 0 / 8 | |
| 3.2.2 | 0 / 8 | |
| 3.2.1 | 0 / 8 | |
| 3.2.0 | 0 / 8 | |
| 3.1.2 | 0 / 8 | |
| 3.1.1 | 0 / 8 | |
| 3.1.0 | 0 / 7 | |
| 3.0.5 | 1 / 7 | |
| 3.0.4 | 1 / 7 | |
| 3.0.3 | 1 / 6 | |
| 3.0.2 | 1 / 6 | |
| 3.0.1 | 1 / 6 | |
| 3.0.0 | 1 / 6 |
v3.2.2
2 findingsThis version was published by a different npm account (stanko.tadic) than the most recent previously approved version (stanko) on 2023-07-11. It has since remained available on npm for 1107 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
2 findingsThis version was published by a different npm account (stanko.tadic) than the most recent previously approved version (stanko) on 2023-07-11. It has since remained available on npm for 1107 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsThis version was published by a different npm account (stanko.tadic) than the most recent previously approved version (stanko) on 2023-07-10. It has since remained available on npm for 1108 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
2 findingsThis version was published by a different npm account (stanko.tadic) than the most recent previously approved version (stanko) on 2023-07-05. It has since remained available on npm for 1113 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
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 (muffinman.io) than the most recent previously approved version (stanko) on 2023-02-21, but muffinman.io is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.1.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 (muffinman.io) than the most recent previously approved version (stanko) on 2022-11-29, but muffinman.io is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.5
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 (muffinman.io) than the most recent previously approved version (stanko) on 2022-11-15, but muffinman.io is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.