react-notifications
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-takeover | AI (maintainer-change): Long-standing (2302d) unremoved publish is inconsistent with real takeover; likely legitimate handoff. | ai | |
| phantom-deps | phantom-dep:acorn | AI (phantom-deps): Old build-tool dep, no malicious behavior found; heuristic false positive for this package. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale 2017 publisher change, long since stable; not indicative of takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same historical maintainer change, stable across many versions since. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): prop-types is a standard, trusted React ecosystem dependency. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.7.4 | 4 / 53 | |
| 1.7.3 | 4 / 53 | |
| 1.7.2 | 4 / 52 | |
| 1.7.1 | 4 / 52 | |
| 1.7.0 | 4 / 51 | |
| 1.6.0 | 4 / 48 | |
| 1.5.0 | 3 / 48 | |
| 1.4.3 | 3 / 48 | |
| 1.4.2 | 3 / 48 | |
| 1.4.1 | 3 / 48 | |
| 1.4.0 | 2 / 49 | |
| 1.3.0 | 1 / 46 | |
| 1.2.0 | 1 / 46 | |
| 1.1.0 | 1 / 46 | |
| 1.0.1 | 1 / 46 | |
| 1.0.0 | 1 / 46 |
v1.7.3
2 findingsThis version was published by a different npm account (tjrexer) than the most recent previously approved version (vn38minhtran) on 2021-12-11. It has since remained available on npm for 1687 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.
v1.7.2
2 findingsThis version was published by a different npm account (tjrexer) than the most recent previously approved version (vn38minhtran) on 2020-09-17. It has since remained available on npm for 2137 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.
v1.7.1
2 findingsThis version was published by a different npm account (tjrexer) than the most recent previously approved version (vn38minhtran) on 2020-09-12. It has since remained available on npm for 2143 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.
v1.7.0
2 findingsThis version was published by a different npm account (tjrexer) than the most recent previously approved version (vn38minhtran) on 2020-09-12. It has since remained available on npm for 2143 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.
v1.6.0
2 findingsThis version was published by a different npm account (tjrexer) than the most recent previously approved version (vn38minhtran) on 2020-04-06. It has since remained available on npm for 2302 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.
v1.5.0
2 findingsThis version was published by a different npm account (tjrexer) than the most recent previously approved version (vn38minhtran) on 2020-03-16. It has since remained available on npm for 2322 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.
v1.4.3
2 findingsThis version was published by a different npm account (minhtranite) than the most recent previously approved version (vn38minhtran) on 2017-06-30. It has since remained available on npm for 3313 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.
v1.4.2
2 findingsThis version was published by a different npm account (minhtranite) than the most recent previously approved version (vn38minhtran) on 2017-06-15. It has since remained available on npm for 3327 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.
v1.4.1
2 findingsThis version was published by a different npm account (minhtranite) than the most recent previously approved version (vn38minhtran) on 2017-06-15. It has since remained available on npm for 3327 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.
v1.4.0
2 findingsThis version was published by a different npm account (minhtranite) than the most recent previously approved version (vn38minhtran) on 2017-06-15. It has since remained available on npm for 3328 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.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.